Send adtribute data to BigQuery

Export your adtribute data to your own BigQuery project, for example to use it in your own BI tools. You set this up yourself: first in Google Cloud, then in Activation. adtribute then adds views of your data to a dataset in your project.

Step 1: Give adtribute access in Google Cloud

1. Log in to the Google Cloud console and open your project.

2. Go to IAM and click Grant access.

   

3. Add adtribute’s pipeline service account as a principal: adtribute-pipeline@adtribute-374219.iam.gserviceaccount.com

4. Assign the role BigQuery Data Editor and click Save.

   

You can grant the role on the whole project or only on the dataset you create in step 2. adtribute shows the same service account, with a copy button, when you create the destination in step 3.

Step 2: Create a dataset

1. Open BigQuery.

2. Click the three dots next to your project name and select Create dataset.

   

3. Give the dataset a clear name.

4. Under Location type, select Multi-region and then EU.

5. Do not set a default table expiration.

6. Click Create dataset.

   

7. Open Dataset info and copy the Dataset ID. It has the form project.dataset.

   

Caution

adtribute rejects a dataset with a table expiration, because BigQuery would delete the views when they expire. A BigQuery sandbox project without billing always sets one. In that case, attach a billing account to the project first.

Step 3: Create the BigQuery destination

1. Go to Activation › Add Action › Create New Destination.
2. Enter a Name and a Description. Both are required.
3. Under Type, select BigQuery. A box asks you to use a dataset in the multi-region EU and to grant the role BigQuery Data Editor to the adtribute GCP Pipeline Service Account. It shows that account with a copy button.
4. Enter the Project ID and the Dataset ID. Split the Dataset ID you copied in step 2 at the dot: my-project.my_dataset becomes Project ID my-project and Dataset ID my_dataset.
5. Click Next.

adtribute now checks the dataset. It must exist, be in the EU multi-region, let adtribute create a view and have no table expiration. If a check fails, adtribute does not save the destination and shows an error.

Note

adtribute refuses a Google Cloud project that another organization in adtribute already uses. If the project belongs to your organization as well, write to support@adtribute.io.

Step 4: Add the action

After Next, the Add Action form opens for your new destination.

1. Enter a Name and a Description.
2. Under Table Reference, select the data to export.
3. Click Add Action.

Table Reference	Description in the app	View in your dataset
Attribution Conversion	Full attribution data attributed by conversion	rep_attribution_conversion_<action ID>
Attribution Click	Full attribution data attributed by click	rep_attribution_click_<action ID>
Conversion Attribution (Conversion)	Conversion attribution data attributed by conversion	rep_conversion_attribution_conversion_<action ID>
Conversion Attribution (Click)	Conversion attribution data attributed by click	rep_conversion_attribution_click_<action ID>
Int Attribution	Aggregated attribution data	int_attribution_<action ID>
Rep Conversion Journey	Data about the conversion journey for each conversion	rep_conversion_journey_<action ID>
Int Conversion	Aggregated conversion data	int_conversion_<action ID>
Int Touchpoint	Aggregated touchpoint data	int_touchpoint_<action ID>
Int Channel	Aggregated channel data	int_channel_<action ID>
Base Event	Base event data	One view per event: base_event_<event key>_<action ID>
Lookup Attribute Source	Lookup Attribute source data	One view per lookup attribute: source_attribute_<attribute ID>_<action ID>

<action ID> is the ID adtribute gives the action. You find it at the end of the action’s Table Name (see below).

An action exports one table reference. To export more, add one action per table reference: go to Activation › Add Action and select your BigQuery destination instead of Create New Destination.

Tip

adtribute can also share specific tables that are not in the list, for example a cohort table. Write to support@adtribute.io and we add it to your destination. It shows up as an action with the Table Reference Custom Table, and its view is named custom_table_<action ID>.

What you find in your dataset

Once you add the action, adtribute creates its view in your dataset. A view holds no copy of the data: each query reads the current data from adtribute.

To get the view’s full name, open the action in Activation. Table Name shows it as <project ID>.<dataset ID>.<view>, with a copy button.

For Base Event and Lookup Attribute Source, the view names also contain the event key or the attribute ID, so they differ from the Table Name. In your dataset, look for views that start with base_event_ or source_attribute_ and end with the same action ID.

Caution

Base Event and Lookup Attribute Source views cover the events and lookup attributes that have data when you save the action. Ones you add later get no view. To include them, delete the action and add it again. The new views carry the new action ID.

What you cannot change after saving

You cannot edit a saved BigQuery destination or action. All fields are locked, including Name and Description, and Save Destination and Save Changes stay disabled.

• For other data, add a new action to the same destination.
• For another dataset or project, create a new destination.
• To stop an export, open the action, click the three-dot menu at the top of the sidebar and select Delete. Confirm with Delete. adtribute removes the action’s views from your dataset.