Dotdigital + Bigquery
Everything you need to connect Dotdigital and Bigquery: how to connect, which data moves, which settings there are and what to do when something goes wrong.
- 1 data flow
- Connect in about 8 minutes
1. Getting started
Prepare both systems first, then connect them in Junipeer.
- about 5 minutes
Prepare Dotdigital
- Open API users in Dotdigital
- Create a new API user
- Leave the generated username unchanged
- Set the password and enable the user
- Save and copy the credentials
- Paste the credentials into Junipeer
- about 3 minutes
Prepare Bigquery
- Open the BigQuery connector in Junipeer
- Click Connect
- Sign in with the correct Google account
- Review and approve access
- Confirm the target project or dataset if prompted
- Return to Junipeer and verify the connection
Connect and test
Enter the details in Junipeer, switch on the flows you need and test with one order before you go live.
Getting started with Junipeer
2. How the data flows
What Junipeer can move between the two systems. The arrow shows which way the data goes.
Junipeer - Customers
3. Settings
The settings you see in Junipeer, in plain words. Open one to read more. The key is the technical name.
You don't need to read them all
In Junipeer every setting has a ? that opens the same explanation next to the form, right when you need it. With the Junipeer MCP your AI assistant can also propose the settings from your own data.
How the Junipeer MCP worksSettings for Dotdigital (13)
| Setting | What it controls | Key |
|---|---|---|
| Consent Attribute Fallback | Choose what happens when the customer attribute doesn't contain consent information . | dotdigital_consent_from_attribute_fallback |
| Consent Attribute Field | Enter the name of the customer attribute that holds the consent text. | dotdigital_consent_from_attribute_field |
| Consent Text | Enter the consent text that is attached to a contact when it is created or updated in Dotdigital. | dotdigital_consent_text |
| Consent URL | Enter the web address (URL) where the customer gave their consent. | dotdigital_consent_url |
| Consent from Customer Attribute | Read the consent text from a customer attribute instead of using the fixed Consent Text . | dotdigital_consent_from_attribute_enabled |
| Contact Identifier | Choose how contacts are identified in Dotdigital. | dotdigital_contact_identifier |
| Default Contact List | Choose a Dotdigital list that contacts are added to by default. | dotdigital_default_list |
| List Attribute Fallback | Choose what happens when the customer attribute doesn't contain a list ID . | dotdigital_list_from_attribute_fallback |
Show all 13 settings
| Setting | What it controls | Key |
|---|---|---|
| List Attribute Field | Enter the name of the customer attribute that holds the Dotdigital list ID(s). | dotdigital_list_from_attribute_field |
| List from Customer Attribute | Read Dotdigital list IDs from a customer attribute , instead of (or in addition to) the list settings. | dotdigital_list_from_attribute_enabled |
| Map Country to Contact List | Add contacts to a specific Dotdigital list based on their billing country . | dotdigital_list_by_country |
| Map Customer Attributes to Data Fields (Store) | Write customer attributes to Dotdigital data fields when contacts are saved. | dotdigital_map_attributes_store |
| Map Customer Fields to Data Fields (Store) | Choose which customer fields are written to Dotdigital data fields when contacts are saved. | dotdigital_map_data_fields_store |
Settings for Bigquery (12)
| Setting | What it controls | Key |
|---|---|---|
| Customer table name | Enter the name of the table in BigQuery where customers are added. | bigquery_customer_table_name |
| Data Source | Enter the source to set on the data that is sent to BigQuery, so you can see where it came from. | bigquery_data_source |
| Dataset ID | Enter the ID of the dataset in BigQuery where Junipeer should create its tables. | bigquery_dataset_id |
| Define Extra Customer Fields | Add extra fields (columns) to the customer table in BigQuery. | bigquery_custom_customer_fields |
| Define Extra Order Fields | Add extra fields (columns) to the order table in BigQuery. | bigquery_custom_order_fields |
| Define Extra Order Rows Fields | Add extra fields (columns) to the order row table in BigQuery. | bigquery_custom_order_rows_fields |
| Include Order Rows | Decide whether order rows are included when orders are sent to BigQuery. | bigquery_include_order_rows |
| Include Personal Information | Decide whether personal information , such as names and addresses, is included when orders are sent to BigQuery. | bigquery_include_personal_information |
Show all 12 settings
| Setting | What it controls | Key |
|---|---|---|
| Include Postal Code and City | Decide whether the customer's postal code and city are included when orders are sent to BigQuery. | bigquery_include_postal_code |
| Map Custom Order Rows Fields | Fill your extra BigQuery order row fields with data from the order rows. | bigquery_map_custom_order_rows |
| Order table name | Enter the name of the table in BigQuery where orders are added. | bigquery_order_table_name |
| Project ID | Enter the ID of your Google Cloud (GCP) project where your BigQuery data lives. | bigquery_project_id |
Did this page help you?