> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cometly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure the AdRoll Conversion API

> Set up the AdRoll Conversion API in Cometly to send the conversions attributed to your AdRoll ads back to AdRoll, server to server.

The AdRoll Conversion API (CAPI) is a server-to-server connection: Cometly sends the conversions it attributes to your AdRoll ads straight to AdRoll, without relying on a browser pixel. A conversion here is an event, meaning an action Cometly tracks for a visitor, such as a lead or a purchase.

This gives AdRoll a cleaner conversion signal for optimization and reporting, which improves match rates and helps your campaigns optimize toward the actions that matter to your business. To set it up, you turn on data sharing, add your server access token, and map your Cometly events to AdRoll events.

## How it works

The AdRoll CAPI is attribution-aware. It only sends conversions that Cometly has already attributed to AdRoll, rather than sending every event for every visitor. For a conversion to qualify, the original click must carry AdRoll's click ID, the `adct` parameter, which AdRoll appends automatically when it serves your ad.

1. A user clicks your AdRoll ad and lands on your site with an `adct` value on the URL.
2. Cometly captures that click and ties it to the visitor.
3. When that visitor converts, Cometly attributes the conversion to AdRoll and sends it through the Conversion API using your server access token.

Because the integration depends on `adct`, only events that can be matched back to an AdRoll click are eligible to be sent.

## Before you start

You need:

* An active AdRoll account with running campaigns, connected to this space as an ad account in Cometly (**Integrations** > **Ad Platforms** > **AdRoll Ads**). Cometly sends each conversion to the AdRoll account that owns the attributed ad.
* An AdRoll server access token for server-to-server conversions. This is not the same as your standard pixel or API key. It is issued by AdRoll staff specifically for S2S conversions, so you may need to request it from your AdRoll account representative or support contact.
* AdRoll tracking links that pass `adct` through to your landing pages. If you already run AdRoll traffic through Cometly, this is typically handled automatically when AdRoll serves the ad.

## Set up the AdRoll Conversion API

**1. Open the AdRoll section of the Conversion API**

In Cometly, go to **Events Manager**, open the **Conversion API** tab, and click the **AdRoll** row to expand it. The **Manage Data Sharing** settings are where you control whether Cometly sends conversions to AdRoll and how your events are mapped.

![Conversion API tab of the Events Manager with every platform row collapsed and a box around the AdRoll row](https://mintcdn.com/cometly/BM7eSn6-ecx8ZzBx/images/guides/conversion-api/ad-roll/04.webp?fit=max\&auto=format\&n=BM7eSn6-ecx8ZzBx\&q=85\&s=1f7410c4f6df8c7449a95b70f372f2a3)

**2. Turn on data sharing**

You see two options:

* **Turn off data sharing**: no event data is sent to AdRoll.
* **Turn on data sharing**: Cometly sends your mapped attributed events to AdRoll.

Select **Turn on data sharing**. The badge on the AdRoll row changes to **Active**.

![AdRoll section of the Conversion API with Turn on data sharing selected and the event mapping card below](https://mintcdn.com/cometly/BM7eSn6-ecx8ZzBx/images/guides/conversion-api/ad-roll/01.webp?fit=max\&auto=format\&n=BM7eSn6-ecx8ZzBx\&q=85\&s=72416633bc9b7be575da20d48615c3bf)

**3. Add your AdRoll server access token**

In the **Configure AdRoll event mappings** card, paste your token into the **AdRoll server access token** field.

About the token:

* It is provided by AdRoll staff for server-to-server conversions.
* Cometly encrypts the token before storing it, so it is never saved in plain text.
* Once a token is saved, the field shows empty again. Leave it blank to keep the current token.
* If you do not have a token yet, contact your AdRoll representative and ask for a server access token for S2S conversions.

![Arrow pointing to the AdRoll server access token field in the Configure AdRoll event mappings card](https://mintcdn.com/cometly/BM7eSn6-ecx8ZzBx/images/guides/conversion-api/ad-roll/02.webp?fit=max\&auto=format\&n=BM7eSn6-ecx8ZzBx\&q=85\&s=71468b339ea4292f6f9f9e8c3e0e7206)

**4. Map your Cometly events to AdRoll events**

A mapping tells Cometly which AdRoll event to send when a given Cometly event is attributed. Each mapping is one pairing: a Cometly event and the AdRoll event it becomes.

![Cometly event dropdown open in a mapping row, with a searchable list of events](https://mintcdn.com/cometly/BM7eSn6-ecx8ZzBx/images/guides/conversion-api/ad-roll/03.webp?fit=max\&auto=format\&n=BM7eSn6-ecx8ZzBx\&q=85\&s=a19e6a96174bf8c3941aff89f19a3062)

To create a mapping:

1. Under **Cometly event**, choose the event you want to send (for example a purchase or a lead).
2. Under **AdRoll event**, choose the AdRoll event it maps to: Page View, Home View, Product Search, Add To Cart, Purchase, High Value Page, Gated Content, Demo Request, Signup Plan, Signup Trial, Contact Sales, Live Chat or Form Fill.
3. Click **Add mapping** to add more pairings.
4. Click the trash icon next to a row to remove a mapping.

Rules to keep in mind:

* Mapping is global for the space. The mappings apply across the whole space, not per campaign.
* Several Cometly events can map to the same AdRoll event. For example, several lead actions in Cometly can all map to **Form Fill**.
* Only mapped events are sent. A Cometly event with no mapping is not passed to AdRoll.
* A row is only saved when both sides are selected.

**5. Save**

Click **Save**. Cometly then sends newly attributed conversions for your mapped events to AdRoll through the Conversion API.

## Check it worked

After you save, Cometly confirms with the message **AdRoll settings saved.** and the badge on the **AdRoll** row reads **Active**. When you reopen the section, your mappings are listed and the token field is empty, with a note that a token is already saved.

## Good to know

* Only attributed events are sent. Cometly does not send unattributed or non-AdRoll conversions through this integration.
* The `adct` click ID is required. Conversions that cannot be matched back to an AdRoll click are not eligible to be sent.
* Changes take effect going forward. Turning on data sharing or updating mappings affects conversions attributed after you save, not historical data.

## Troubleshooting

> [accordion] No conversions are showing up in AdRoll
>
> Confirm that data sharing is turned on, your server access token is saved, and you have at least one event mapping saved. Then check that your AdRoll traffic carries `adct` to your landing pages. If `adct` is missing, Cometly cannot attribute the click to AdRoll and the conversion is not sent. Also check that the AdRoll ad account that runs the ad is connected to this space.

> [accordion] I do not have a server access token
>
> The token is issued by AdRoll for server-to-server conversions and is separate from your pixel. Contact your AdRoll account representative or AdRoll support to request one.

> [accordion] My token was rejected or stopped working
>
> Tokens can expire or be rotated on AdRoll's side. Request a new server access token from AdRoll, paste it into the **AdRoll server access token** field, and click **Save** again.

> [accordion] I want one AdRoll event to capture several Cometly events
>
> Map each Cometly event to the same AdRoll event. Several Cometly events can point at a single AdRoll event.

## Frequently asked questions

### Does Cometly send the purchase value to AdRoll?

Yes, for Cometly events you map to the AdRoll **Purchase** event. Cometly sends the purchase amount as the conversion value, in your space's currency. Events mapped to other AdRoll events are sent without a value.

### What data does Cometly send to AdRoll with each conversion?

Each conversion carries the AdRoll event you mapped, the time of the event, the `adct` click ID, the page URL and the visitor's IP address. Cometly also includes the contact's email address when it has one.

### Can I stop a single event from being sent to AdRoll?

To stop a whole event type, remove its mapping and click **Save**, because only mapped events are sent. To hold back individual events (for example, a visitor who opted out of data sharing), see [Exclude an event from the Conversion API](https://docs.cometly.com/guides/conversion-api/exclude-an-event.md). That option keeps the event out of every ad platform, not only AdRoll.

## Next steps

* [Connect AdRoll to Cometly](https://docs.cometly.com/integrations/ad-platforms/ad-roll.md)
* [Exclude an event from the Conversion API](https://docs.cometly.com/guides/conversion-api/exclude-an-event.md)
* [Set up the Conversion API for another ad platform](https://docs.cometly.com/guides/conversion-api/overview.md)
* [Contact Cometly support](https://docs.cometly.com/support/contact.md)

Still have questions or need a hand? We're happy to help. Reach our team at [support@cometly.com](mailto:support@cometly.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.