Combined Report
The Combined Report pipeline can be used to request and retrieve a combination of both network (such as cost) and tracker stats (such as installs and revenue). This data is combined using special dimensions and metrics which are based in tracker and network data, and tabulated according to an additional logic behind the scenes. Read more about this here
For example, the name of a specific campaign in the tracker may be slightly different from the name of the campaign as pulled from the ad network. So if you run a tracker report and a network report and join the results, you may get split rows for the campaign, where one row has network stats and the other has tracker stats. But if you run a combined report (using the unified_campaign_name dimension), Singular makes sure you can still get both network stats and tracker stats in the same row for the campaign.
| In situations where the same stat is offered by both the network and the tracker, e.g., the number of installs per campaign in a given date range, the combined metric gives you a single source of truth, intelligently picking either the tracker stat or the network stat based on standard industry usage. |
For example, the custom_installs metric contains the number of installs from the tracker, unless it is a Self-Attributed Network (SAN) such as Facebook or Twitter, in which case the network stat is more important, and custom_installs contains the network metric.
Configuring the Credentials
Select the account credentials which has access to relevant Singular data from the dropdown menu & Click Next
Setting Parameters
| Parameter | Description | Values |
|---|---|---|
Insert Mode |
Required This refers to the manner in which data will get updated in the data warehouse, with 'Delete' 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. |
Default Value: Upsert |
Number of Days |
Required Number of days for which you wish to get the data in each run. NOTE: A single request can query up to 30 days and has a maximum of 100,000 queried records. Requests querying more than 100,000 records will not succeed and will require additional filtering. |
Integer value (Recommended value 2) |
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.