> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/adform.md).

# AdForm

How to connect AdForm to Roivenue, what the default setup downloads, and how the figures are put together.

Adform display and programmatic. The Roivenue connector downloads daily impressions, clicks and cost down to banner level, plus the conversions Adform attributes to them.

## Setting up the connector

Add a Adform connector in Roivenue and choose Connect to Adform. Roivenue sends you to Adform to sign in and approve access. There are no keys to copy.

### Setup options

| Option               | Default    | What it does                                           |
| -------------------- | ---------- | ------------------------------------------------------ |
| Tracking point id    | none       | Which Adform tracking point counts as your conversion. |
| Conversion type name | `purchase` | What that conversion is called inside Roivenue.        |

## What the default setup downloads

Three jobs. One brings impressions, clicks and cost per banner and day, a second brings conversions and sales, and a third downloads the hourly feed behind synthetic impressions.

### Where the values land

| AdForm field  | Roivenue column |
| ------------- | --------------- |
| `campaign`    | adCampaign      |
| `order`       | adGroup         |
| `banner`      | adName          |
| `lineItem`    | lineItem        |
| `media`       | media           |
| `impressions` | impressions     |
| `clicks`      | clicks          |
| `cost`        | cost            |
| `conversions` | conversions     |
| `sales`       | conversionValue |

Adform's order becomes the ad group in Roivenue and the banner becomes the ad, while line item and media arrive as their own dimensions rather than being folded into the campaign hierarchy.

Conversions come from the tracking point chosen at setup, so choosing the wrong one produces plausible but wrong numbers.

The main jobs reprocess the last 14 days on every run, which is longer than most connectors and reflects how late Adform settles its figures.

## Available columns

The table above is what the recommended template downloads. Every column this connector can bring back is listed on [AdForm - Supported Columns](/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/adform/adform-supported-columns.md).

Adding one means editing the connector in the Advanced Editor, which stops that connector receiving template updates.

## Synthetic impressions

Alongside the daily figures, this connector downloads a conversion feed that Roivenue uses to build synthetic impressions.

Ad platforms report conversions that Roivenue never saw as a web session, because of ad blockers, cross-device journeys or conversions uploaded from a CRM. Left alone those orders look like they came from nowhere, and paid media gets undercounted. The synthetic impression stands in for the missing visit so path analysis and attribution see a complete journey.

There is nothing to configure. It comes with the connector, and it is why the setup creates more than one job.

## How far back the data goes

Adform serves up to 13 months of history, so a new connector can backfill a little over a year.

## Troubleshooting

<details>

<summary>Conversions are zero or clearly wrong</summary>

Check the tracking point id on the connector. It is entered by hand at setup, and a wrong id either returns nothing or returns a different action than you expect.

</details>

<details>

<summary>Recent numbers keep changing</summary>

That is expected. The jobs reprocess 14 days on every run because Adform continues to adjust recent figures.

</details>