Connect this destination to send warehouse conversion events, such as purchases, add-to-carts, and leads, to Viant for campaign attribution and optimization. You do not need an audience.

This destination writes to your Viant account and is a good fit when you want to:

• Attribute online or offline conversions to your Viant DSP campaigns
• Use a warehouse table that has one row per conversion with a transaction ID and timestamp
• Match conversions on email, physical address, IP, mobile ID, cookie ID, or Viant click and impression IDs

This maps to GrowthLoop Syncs:

Do not use this workflow to add contacts to a targeting segment. To activate customers for targeting, use Viant.

Prerequisites

Make sure you have:

• A Viant DSP account. See Viant if you need one.
• Username and Password partner credentials for GrowthLoop. Ask your Viant representative. These are not your regular Viant login.
• Your numeric Viant Account ID and one or more numeric Advertiser IDs. Ask your Viant representative if you do not have them.
• A warehouse table with your conversion events. Each row needs a transaction ID, an event type, a timestamp, and at least one customer identifier.

Set up Viant Conversions as a destination

1. In GrowthLoop, click the Destinations tab on the left sidebar.
2. Click New Destination in the top right corner.
3. Search for Viant Conversions and click Add Viant Conversions.
4. Enter the required information, then click Create.

⚠️

Warning

Use the GrowthLoop partner credentials your Viant representative provides. Do not paste a regular Viant user login.

GrowthLoop signs in to Viant and checks access to the Viant Conversion API without sending any data. Viant Conversions then appears in your list of connected destinations.

📘

Note

You can reuse the same Username and Password for a Viant audience destination and a Viant Conversions destination.

Create a sync in GrowthLoop

Create a sync from a warehouse table to send conversion events to Viant. See Syncs for information on how to complete those steps.

Select an Object Type:

When you configure the sync:

• Update Rule: Choose Insert only. Conversions are one-time events, and GrowthLoop does not update or remove conversions it already sent.
• Dataset/Table: Select the table that holds your conversion events. Use one row per conversion.
• Connection: Select your Viant Conversions destination.
• Object Type: Select Conversions.
• Match Field: Map one of the customer identifiers, such as Email.

GrowthLoop rejects the field mapping unless you map Transaction ID, Conversion Event Type, Conversion Timestamp, and at least one customer identifier.

Required event fields

Customer identifiers

Map at least one of the following. A single row can include more than one identifier, and GrowthLoop sends every valid identifier on the row.

Optional conversion fields

Here is an example Purchased Items value:

[
  {"item_id": "SKU-123", "price": 25.00, "quantity": 2, "product_name": "Running Shoe"},
  {"item_id": "SKU-456", "price": 25.00, "quantity": 1}
]

See Viant's Conversion API for field definitions.

Sync behavior

This is what GrowthLoop writes when you sync conversion events to Viant.

Confirm the sync was successful

When the run finishes, confirm you can use the data in Viant.

• Conversion sync: Viant queues conversions and processes them asynchronously. Confirm the conversions in your Viant campaign reporting, or ask your Viant representative.

This workflow does not create a targeting segment.

In GrowthLoop, confirm the sync appears in the Syncs table. See Syncs for more information.

Congrats on successfully syncing conversions to Viant!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.