How Gowit Works

GoWit is a retail media platform that helps online marketplaces earn money using onsite and offsite ads. Sellers can promote their products directly within the shopping experience through native, display, or video ads.. The platform uses real-time product and shopper data to show the most relevant ads.

At its core, GoWit is an ad decision and measurement engine. It takes in advertiser and product data, checks available ad spots against campaign targets, and delivers the best-ranked ads to display on a site or app. GoWit supports many ad types—like Sponsored Product, Display, and Video—and can connect through an API or optional SDKs, so developers can keep full control of layout and user experience.

From Setup to Launch

1. Set Up Advertiser & Product Feed: First sync sellers (advertisers) into GoWit. This is enough to start Sponsored Display. Add the product catalog later for Sponsored Product ads and better attribution.
2. Create Placements & Campaigns: Define ad slots on your site (e.g. homepage banner, search results) and get placement IDs. Create test campaigns so ads can return during integration.
3. Implement Ad Calls: From your backend, call GoWit’s ad API with placement_id, session_id, and page context (like top product_ids). Backend handles API calls; frontend just renders ads. Keep API keys server-side and handle empty responses.
4. Track Events: Send impression and click events with the ad_id. For conversions, send all completed orders—GoWit handles attribution (post-click/post-view, direct/indirect). If auto-impression is on, you still send clicks and conversions.
5. Validate in Staging: Use test campaigns to confirm product feed, ad delivery, and event tracking work. Fix any data or logic issues before launch.
6. Go Live: Switch to production API and credentials, recreate placements and campaigns, and run a final product sync. You may soft-launch to a small traffic slice and monitor logs before full rollout.

Roles & Responsibilities

Marketplace (Partner):

• Build and send advertiser and product data to GoWit.
• Add code to request and display ads in defined placements.
• Send tracking events (impression, click, conversion).
• Keep data current and ensure ads don’t break or slow the site.
• Test everything in staging and fix any data or tracking issues.

GoWit:

• Provide API docs, SDKs, credentials, and a staging environment.
• Set up sample entities (like test advertisers or placements).
• Offer technical support and QA tools (staging dashboard, Dev Tools).
• Review the integration before launch to confirm ads and events work correctly.

Development Time Estimates

To help with planning, here are rough estimates of the development effort required for each integration module. (Actual times may vary based on complexity and the developer’s experience, but this gives a ballpark assuming one developer working sequentially on each task.)

Integration Module	Estimated Time	Details
Advertiser Integration	~1–2 days	Create or map seller accounts into GoWit, possibly via API or one-time import. Initial setup can be quick, but full automation may take longer.
Product Integration	~2–3 days	Set up automated export or API push of product catalog data, including formatting and testing.
Ad Placement Setup	~1–2 days	Define ad slot positions on site and configure them with GoWit; includes front-end layout adjustments for new ad spaces.
Ad Request & Rendering	~2–3 days	Implement the code to call the ad API and properly render the returned ad content in the UI.
Impression & Click Tracking	~3–4 days	Capture when ads are viewed or clicked and send those events to GoWit; includes testing on various browsers/devices and handling edge cases like multiple impressions.
Conversion Event Tracking (Sales)	~2–3 days	Post conversion events from your order system to GoWit’s API — include all sales, attribution will be handled automatically.
Authentication Integration (optional)	~2–4 days	Only if needed – e.g., implementing SSO or JWT-based login for advertisers to access GoWit’s dashboard through your system. If advertisers will log in via GoWit separately, this might not be required initially.
Payment Integration (optional)	~2–4 days	Only if needed – e.g., integrating a payment method or credit system for advertisers to fund their ad accounts. Many partners skip this at launch and manage billing offline or manually.
Staging & QA Validation	~1–2 days	Time to test everything end-to-end in the staging environment and fix any issues found before going live.

---

Note: These estimates assume one developer working sequentially, needing about 14–20 days. If tasks are done in parallel (e.g. one developer handles front-end ad rendering while another manages back-end feed integration), the timeline can shrink to around 10–12 days. Always leave extra time for code reviews, testing, and unexpected changes.