Advertiser Schema
What is an Advertiser?
In GoWit’s platform, an Advertiser is the seller, vendor, or supplier on your marketplace who runs ads. Each seller must be mapped to a GoWit advertiser record with a unique ID and name so GoWit can recognize them as the ad owner.
The advertiser record acts as the seller’s ad account, holding all campaigns, budgets, and performance metrics, and making sure each ad campaign is tied to the correct seller.
Why Advertiser Setup Matters:
Advertiser onboarding is the first step in any GoWit integration—before products or campaigns—because nothing works without it.
- Every product record must reference a valid advertiser_id, or it can’t be created.
- Every ad campaign belongs to a specific advertiser; campaigns can’t be created without one.
- Even ad types without product data (like Sponsored Display banners) need at least one advertiser.
👉 Advertisers are the foundation of GoWit’s data model—set them up first so products and campaigns can link correctly.
Custom Advertiser Option
If you encounter issues with advertiser integration — for example, if you are blocked, or if your platform does not maintain separate seller accounts (all products are sold under a single seller, but ad management needs to be separated by account) — you can use the custom advertiser feature.
This allows you to define advertiser entities flexibly, even without a corresponding seller account in your platform.
📌 For more details, please refer to the Advertiser Types Documentation.
Required Fields
Each advertiser record has several required fields that must be provided to successfully integrate with GoWit:
| Field | Description |
|---|---|
| id | Unique advertiser ID in GoWit (usually your seller ID). Must stay consistent across all integrations to link products and campaigns. |
| name | The advertiser’s display or company name, shown in dashboards and reports. Use a clear, human-readable name. |
| status | Controls ad eligibility. Must be ACTIVE for products or campaigns to run; other statuses (like DELETED) make the advertiser ineligible. |
Optional Fields
Additional optional fields can enrich advertiser profiles or affect interactions:
| Field | Description |
|---|---|
| Contact email for the advertiser. Needed for dashboard invites and notifications. Campaigns can run without it, but the advertiser won’t get notifications or reports. | |
| language | Preferred language code (e.g. EN, TR) for UI and communications. Defaults to the marketplace setting if not provided. |
| time_zone | Present in the schema but has no operational effect; scheduling and reporting happen at the marketplace level. |
| process_id | Optional batch identifier. Useful for full syncs to deactivate advertisers not included in a batch. Not needed for everyday operations. |
Key Behaviors of Advertisers in GoWit
Once advertisers are set up, keep in mind these key rules:
- Scope of Campaigns and Budget – Campaigns, budgets, and products are isolated per advertiser. No cross-sharing of funds, products, or attribution.
- Reporting Isolation and Access Control – Advertisers are tenancy boundaries. Vendors only see their own performance; marketplace admins can view all.
- Feature Enablement per Advertiser – Features (e.g., advanced targeting, ad formats) can be restricted or enabled per advertiser.
- Manual and Bulk Creation – Advertisers can be added manually via dashboard/admin panel or bulk-synced via API. Both follow the same schema.
Summary
The Advertiser schema is the cornerstone of GoWit’s retail media integration. It:
- Defines seller accounts in the ad platform.
- Serves as the base for products, campaigns, budgets, and reports.
- Requires careful setup of required fields (
id,name,status, etc.). - Can be enriched with optional fields (
email,language, etc.).
✅ Always set up advertisers first and keep their status ACTIVE for those who should advertise, as this unlocks the rest of the retail media workflow.