Skip to main content
A brand card is the Agentic Branded Content (ABC) article served to an AI agent: a compact, self-contained piece of sponsored branded content. It is what the agent reads. Its eligibility decides on which fragments it may serve.

​
Create a card

Open Cards, then New card. You do not write card HTML: you give doubleshift source material and it generates the card. Choose the Card language and, optionally, a Brand hint, then one input:
  • From a PDF: a press release or product sheet, 10 MB at most.
  • From text / structured data: paste a press release, product data or JSON.
  • From a URL: doubleshift fetches the page server-side and builds the card from its content.
Create manually lets you fill in every field yourself instead. Every path ends the same way: doubleshift validates the card and saves it as a draft. Review the preview, edit the fields under Edit if needed, then Save changes. The preview shows the card’s content; what your page delivers is checked in Verify and troubleshoot. The fields, their validation and the HTML they become are in Card format.

​
Eligibility: where a card may serve

Open a card and use its Eligibility section. Fragments are grouped by site, each with its name, its reference when it has one, and (paused) when it is paused.
1

Select the fragments

Check the fragments the card may serve on. Leave every box empty to make it eligible everywhere in your account, including fragments you create later.
2

Save eligibility

Save eligibility replaces the card’s whole list with what is checked. To lift every restriction, clear all the boxes and save.
Several cards can be eligible on the same fragment. Eligibility is an allow-list on the card, not an approval step on the fragment, and it gives a card no priority over the other eligible cards. It never infers a page topic or matches a GAM family on its own. How doubleshift picks one card among the eligible ones is in selection. Platform cards are cards managed by doubleshift: they follow the same eligibility rule and are read-only in your console.

​
Activate, archive or delete

Only active cards serve. Under Status:
  • Activate puts a draft or archived card into delivery.
  • Archive takes an active card out of delivery and keeps it. Activate it again at any time.
  • Delete removes the card and its eligibility.
A change applies on the next call to the fragment endpoint (no cache). When no card is active and eligible for a page, the endpoint answers no-fill (204) and the page renders unchanged.

​
Confirm that it serves

A card can serve on a page when it is active and its eligibility is empty or includes the fragment the page resolves to; the site’s routing rules and default decide that fragment (Sites and fragments). When several cards are eligible, a page can get another one of them (selection). To check a page, call the endpoint as in Verify and troubleshoot. Reporting then counts the served calls by card.