Junipeer sends your webshop's orders, and on some integrations your customers, to tables in your own Google BigQuery project. Choose the columns first: adding them after a table is created doesn't work.
1. Connect BigQuery
You need two things from Google Cloud:
Project ID: the ID of the Google Cloud (GCP) project where your BigQuery data lives.
Dataset ID: the dataset where Junipeer should create its tables. A simple name works, for example
junipeer.
Open the integration and go to Get Started → Connect Systems.
For BigQuery, fill in Project ID and Dataset ID.
Click Connect to BigQuery and log in with Google.
The setup jobs in step 3 create the dataset and the tables.
2. Choose the columns before the tables exist
The settings are in Configure > Settings, in the settings of Export Orders to BigQuery. If your integration also sends customers, the customer settings are on Export Customer to BigQuery. Click the ? next to a setting for details.
Setting | What it decides |
|---|---|
Include Order Rows | Whether order rows are included |
Include Personal Information | Whether personal information, such as names and addresses, is included |
Include Postal Code and City | Shown when personal information is No. Adds postal code and city, but no street address |
Define Extra Order Fields, Define Extra Order Rows Fields, Define Extra Customer Fields | Extra columns. Each row is a Field name and a Data Type: BOOLEAN, INT64, NUMERIC, STRING or TIMESTAMP |
Order table name, Customer table name | The table names. Defaults: |
Data Source | A label on the data that shows where it came from, usually your e-commerce platform or shop name |
Write field names with a–z only, without spaces or special characters, for example field_name or fieldName.
The extra field settings only create the columns. Filling them with data is a separate step. Extra order row columns are filled in Map Custom Order Rows Fields, where the names must match exactly, including upper and lower case.
If you change a table name later, run that table's setup job again.
3. Create the tables
On the Flows page, run these jobs once, before the first export. They have no fields to fill in.
Setup Order Table in Bigquery creates the dataset and the order table.
Setup Customer Table in Bigquery creates the dataset and the customer table. Run it if you send customers.
Check on the Tasks page that each job finished.
4. Test with one order
On the Flows page, click Export One on Export Orders to BigQuery.
Enter the Order ID: the order's ID in your webshop. For Magento, it is the entity_id.
Check the run on Tasks and Logs.
Find the order in your BigQuery order table and check the columns.
Test a customer the same way on Export Customer to BigQuery, with a Customer ID.
5. Send older orders
Click Export Many on Export Orders to BigQuery and pick an earlier Date. The run loads orders created or updated after that time.
Start with a short period, for example one week, and check the result before you go further back. A large backfill can take time.
If Exclude Orders created before this date is set, orders created before that date are not sent, whatever date you pick.
Send older customers the same way with Export Many on Export Customer to BigQuery.
6. Schedule the export
Under Configure > Scheduling, add a scheduling rule for Export Orders to BigQuery, and one for Export Customer to BigQuery if you send customers. Each run loads what was created or updated since the last run. The Time History page shows the date the next run starts from. See Scheduling.
When to contact support
Contact support@junipeer.io:
for help filling extra order row columns. Send an order ID, so support can find the right attributes for you to map.
if a setup job or an export keeps failing. Include the integration name, the flow, an order ID and the message from Logs.