GET /api/v1/campaigns/fetch, and the API uses them to return campaigns that are most relevant to the current user and page context. Providing accurate targeting data improves match quality, which leads to higher engagement and better results for advertisers on your platform.
Geographic targeting
Pass the user’s country as a two-letter ISO 3166-1 alpha-2 code in thelocation query parameter.
Campaigns can be targeted to any country worldwide. If you do not pass
location, the API returns campaigns without applying geographic filtering.
Device targeting
Pass the user’s device type in thedevice query parameter. The accepted values are:
User-Agent header or a device detection library, rather than relying on client-side JavaScript, so the parameter is always present when the request is made.
Content category targeting
Campaigns are associated with a content category that describes the subject matter of the advertised product or service. While category is not a direct query parameter on the fetch endpoint, the campaign objects returned include acategory field you can use to filter or contextually style ads on your page.
The full set of supported categories is:
Combining all three dimensions
For best results, passplacement, location, and device together on every fetch request:
limit parameter is optional (default 10, max 100) and controls the maximum number of campaigns returned. Reduce it when you only have room to display a small number of ads.
When you track an impression or click, pass the same
location and device values you used during the fetch. This keeps targeting data consistent across the campaign lifecycle and ensures accurate performance reporting for advertisers.