Rollout consists of several stages:

• Publisher account setup — takes just a few minutes. You get instant platform access. You need a product feed in Google Merchant Center format (with an additional Supplier field).
• Store integration — your IT team builds server-to-server endpoints and places placements on the site. We do the first placements together to start off right.
• Token and placement link generation in the MageAds platform — a few minutes.
• Launch of test campaigns — duration depends on the number and type of placements.

What’s typically the trickiest part? Sometimes product placement integration (e.g. showing the sponsored product in search results or category listings) requires a bit more attention from IT. Our guideline includes examples — but specific store configurations sometimes require deeper investigation.

The integration is well documented in our guideline — your IT team will handle it without issues. You’ll find concrete script examples there. Documentation: mageads.com/docs/api/overview

Of course. We set up a test account on our production environment — you can connect it to your test store. It’s exactly the same environment as production, so the tests are fully representative.

What you can test:

• No ad — simulate various scenarios: no budget, no active campaign, untargetable audience.
• No system response — connection is tested as part of endpoint integration described in documentation.
• Various display scenarios — any campaign and placement configuration in the test account.

We assume something will always be displayed. If there’s no active campaign — the spot simply disappears, as if the banner was never there. No empty space disrupting the layout.

It’s a good practice to set up a permanent fallback campaign for Display ads. For Sponsored Products, this doesn’t apply.

Yes, if you decide so. You can assign multiple campaigns to each placement, or just one at a time.

For Display — campaigns are served by impression according to priorities: first House Campaigns, then those with the highest CPM.

Absolutely. On the homepage you might see a classic branding campaign — display or video. On a product page — ads for related products.

When creating a campaign you choose specific destinations: category, URL, product, search results.

Yes. Our integration ensures content responsiveness and works in the vast majority of cases. For very specific placements, we can use a dedicated mobile version of the banner.

Everything can be previewed and verified before publishing a campaign.

As part of integration we set an appropriate timeout (400–500 ms) for our server response. If we don’t respond in that window, the page loads normally without waiting.

In practice we respond in 120–200 ms, so users won’t notice any difference. Scripts run asynchronously, so page loading isn’t blocked.

Details in docs: mageads.com/docs/api/overview#timeout

Every external campaign must be approved by you — nothing appears without your consent. No strings attached: you can reject all campaigns if you see fit. Of course, we’ll work to send you campaigns aligned with your offering.

How it works by campaign type:

• AUTOPROMO (in-house) campaigns — visible immediately after creation.
• Sponsored Products (external) — displayed automatically.
• Display / Video (external) — always require approval. Marked REVIEW in the panel.

Yes, instantly. Just click the Deactivate button in the panel — the campaign is off in about 5 seconds.

Anyone with panel access can do this — both your team and our system admins.

Yes. You can see the full delivery history for any date range, including the products the ads referred to. You get both the full campaign view and per-product statistics.

One limitation: for Display campaigns, if the banner creative is changed mid-flight, statistics show aggregate data — without breaking it down between before and after the change.

They can, but you have full control. As part of campaign approval, you decide whether to accept campaigns that allow exiting your store.

You can also configure whether the click opens in a new tab or stays in the same one. You check this setting in the URL tab when reviewing Display campaigns.

Every ad’s content goes through your campaign approval process, so you have full control over what appears. There’s no way for anything you haven’t approved to show up on your site.

In the standard model — yes. But our integration is based on server-to-server communication and supports configuring reverse proxy.

This way ads are served from your domain, and the browser treats them as part of the site’s content. Tools like Ad Block don’t detect them.

Importantly — this doesn’t require any messages asking users to disable Ad Block. The ads just work.

Yes, if the advertiser opts into targeting. We have plenty of options — best to check our knowledge base for the full picture: knowledge base — targeting

• GeoTargeting — targeting by location (regions, cities, area exclusions).
• Technical Targeting — targeting by device, browser, operating system.
• Frequency Capping — limiting how many times the same ad is shown to one user in a given period.
• Profile Targeting — targeting based on purchase behavior (e.g. browsed products, cart additions, order history) with group exclusions.

Currently targeting info is visible in campaign details. During approval you review the campaign anyway — if the targeting tabs are active, you can see immediately that it’s enabled and check what it consists of.

We’re open to UX suggestions — e.g. adding icons signaling active targeting directly in the campaign list.

Yes. Just remove the chosen products or their entire category from the product feed imported to the platform. Without that data, the system cannot connect the product to a user, so targeting it won’t be possible.

For basic ad operation, we practically don’t need any personal data. We only need information that the ad was served (basic KPIs, e.g. impression count).

Optional data (only collected with user consent and if you choose to deploy the relevant trackers):

• First-party cookies, session identifiers, mobile device identifiers.
• IP address, referrer (entry page).
• Behavioral data: browsed products and categories, search interactions, cart activity.
• Purchase history and signals from logged-in users.

You decide which trackers to enable and what data to share. If you opt into targeting, it’s worth adding at least the add-to-cart tracker (without passing full transaction value) — it’s an important signal for campaign effectiveness.

Absolutely. This data gives additional targeting options, but is completely optional. The system works fine without it.

Trackers that collect and pass data require user cookie consent — exactly like other analytics or advertising tools in e-commerce. If a user doesn’t consent, trackers don’t fire and you don’t pass us any data.

What happens without consent? Ads still display, just not personalized. If a campaign requires targeting and the user doesn’t fit any segment (because we don’t have data on them) — they simply won’t see that campaign, but may see a different, non-targeted one.

It works the same way as any other ad portal: no cookie consent doesn’t mean no ads — it just affects which ads appear.

In incognito mode we cannot identify the user. Incognito creates a session with a randomly generated ID. All cookies from that session are deleted on close.

Even if the user gave consent during that session and we collected behavior data — on their next visit (again in incognito), they’ll have a different, random ID. There’s no way to link these sessions.

In line with GDPR requirements, data is pseudonymized and only in this form aggregated into segments (user profiles). We don’t process personal data that enables direct identification.

No longer than 60 days from the user’s last ad interaction.

Data is used exclusively within the MageAds platform. The only exception is integration with Google Ad Exchange — but only if you request it (it’s optional). In that case, some data goes to Google, which requires appropriate user consent in your cookie policy.

Full control. You decide which trackers you enable and integrate — which determines what data reaches us. You can disable any tracker at any time.

The consequence is reduced targeting scope, but ads still work.

Consent is required only when activating data-collecting trackers. Ads without trackers can run without additional consents beyond what you already have in your cookie policy and consent management.

You add to your cookie banner only those elements you’ve linked to specific trackers.

Yes, you have access to the full set of KPIs in real time — broken down by campaigns and advertisers. We’re constantly adding new metrics.

The list of available metrics is here: knowledge base — Main Dashboard

Full control over what is advertised stays on your side — you approve or reject campaigns. Reporting data is collected automatically, and the product feed can be automatically updated.

We’re responsible for delivering campaigns you’ve approved and for maintaining and developing the platform you’ll use.