Skip to main content

Advertiser Integration

Where Can I See the Advertisers I Sent?​

Platform UI

  • Navigate to Dashboard → Advertisers to view all advertisers.

Data Source Logs

  • If you're using the Data Source option for integration, you can find the update logs in the Data Source section.

Why Can’t I Activate an Advertiser?​

Our platform distinguishes between the status you send and the status we serve:

Auto‑activation disabled

  • Each marketplace has a flag in its config (e.g. activate_advertisers_during_integration: false).
  • Advertisers created while this flag is false are imported with status Paused and cannot be flipped to Active until an admin changes the flag or the advertiser accepts an invite.

Integration Status

  • Represents the status included in your payload (e.g., "ACTIVE", "PAUSED", "DELETED").
  • Controlled by you.

Status

  • Indicates whether the advertiser is live in our system (ACTIVE ↔︎ PAUSED).

Frequent Causes​

Platform status: PAUSED (even though integration_status = "ACTIVE")​

Likely reason:
The marketplace’s “auto-activate advertisers during integration” flag is disabled by default.

What you can do:
Contact if you need new advertisers to go live automatically.

Platform status: Advertiser missing altogether​

Likely reasons:

  • One or more required fields (resource_id, name, contactEmail) were empty or invalid.
  • The resource_id duplicated an existing advertiser.

What you can do:
Correct the payload and resend. Ensure all resource IDs are unique across your feed.

Platform status: 4xx response on upload​

Likely reasons:

  • JSON schema validation failed (check the error body).
  • Your authentication token has expired.

What you can do:

  • Fix the field noted in the error message.
  • Refresh your authentication token.

What should be the update interval for advertiser integration?​

Applies to feed‑based integrations only
If your marketplace use advertiser feed, follow the schedules below.
If your marketplace does not use a feed and instead pushes advertisers via the API, you may call the API as often as you like; cadence is entirely up to the caller.

IntervalCron exampleWhen to use
15 min (default)*/15 * * * *Normal production traffic; balances freshness and load
60 min0 * * * *Low‑volume marketplaces, proofs of concept

Guidelines

  1. Keep the default 15‑minute schedule unless you have a compelling reason to change it.
  2. The integration is idempotent, but running it too often can congest the message queue for large catalogs.

For marketplaces that manage advertisers exclusively through the API (no feed), coordinate your own trigger frequency—e.g., on each advertiser change event or via a periodic job that suits your traffic pattern.