User Ad Distance Performance Report
The User Ad Distance Performance report can be used to request and retrieve statistics aggregated by the user’s distance from your location extensions. Each DistanceBucket shows all impressions that fall within its distance. As a result, an impression will contribute to the stats for all DistanceBucket objects that include the user’s distance.
You can read more about this end-point on the Google Ads API documentation page here
Configuring the Credentials
Select the account credentials which has access to relevant Google Ads data from the dropdown menu & Click Next
Data Pipelines Details
- Data Pipeline
-
Select User Ad Distance Performance Report from the dropdown
- Customer
-
Select one or more customers from the drop-down
| All customers which your credentials have access to should be available here. If they are not, please check the credentials selected / configured by you. While you can add multiple customers, the table size may become too large and so it is advisable to add one customer per pipeline and use Union queries in the data warehouse to join the data for consumption |
- Attributes, Segments and Metrics
-
Select the attributes, segments and metrics you would like to fetch from the Google Ads platform. You can click on View Schema anytime to see the schema of the table being created.
| Each of the selected attribute / metric will create one or more columns in the database table in the destination warehouse. |
Setting Parameters
| Parameter | Description | Values |
|---|---|---|
Delete or Append |
Required This refers to the manner in which data will get updated in the data warehouse, with 'Upsert' selected, the data will be upserted (only new records or records with changes) and with 'Append' selected, all data fetched will be inserted. Selecting 'Replace' will ensure the table is dropped and recreated with fresh data on each run. Recommended to use "Upsert" option unless there is a specific requirement. |
{Upsert, Append, Replace} Default Value: Upsert |
No of Days |
Required Number of days for which you wish to get the data in each run. |
Integer value (Recommended value 30) |
Include Zero Impressions |
Required Indicates whether data for those ads / campaigns is to be included where impressions are 0. |
{True, False} |
Datapipeline Scheduling
Scheduling specifies the frequency with which data will get updated in the data warehouse. You can choose between Manual Run, Normal Scheduling or Advance Scheduling.
- Manual Run
-
If scheduling is not required, you can use the toggle to run the pipeline manually.
- Normal Scheduling
-
Use the dropdown to select an interval-based hourly, monthly, weekly, or daily frequency.
- Advance Scheduling
-
Set schedules fine-grained at the level of Months, Days, Hours, and Minutes.
Detailed explanation on scheduling of pipelines can be found here
Dataset & Name
- Dataset Name
-
Key in the Dataset Name(also serves as the table name in your data warehouse).Keep in mind, that the name should be unique across the account and the data source. Special characters (except underscore _) and blank spaces are not allowed. It is best to follow a consistent naming scheme for future search to locate the tables.
- Dataset Description
-
Enter a short description (optional) describing the dataset being fetched by this particular pipeline.
- Notifications
-
Choose the events for which you’d like to be notified: whether "ERROR ONLY" or "ERROR AND SUCCESS".
Once you have finished click on Finish to save it. Read more about naming and saving your pipelines including the option to save them as templates here
Still have Questions?
We’ll be happy to help you with any questions you might have! Send us an email at info@datachannel.co.
Subscribe to our Newsletter for latest updates at DataChannel.