Raw Conversions
This Raw Conversions pipeline can be used to request and retrieve a list of conversions.
Read more about the Raw Conversions pipeline here
Configuring the Credentials
Select the account credentials which has access to relevant Everflow data from the dropdown menu & Click Next
Setting Parameters
Parameter | Description | Values |
---|---|---|
Number of Days |
Required Enter the number of days for which you wish you get the data in each run. |
'NUMBER' |
Insert Mode |
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. |
Default Value: Upsert |
Upsert Key |
Dependent Required Specify comma separated Upsert Keys based on which data is to be upserted. |
'Upsert Key' |
Columns |
Required Select the columns that are to be included in the report. Multiple columns can be selected. At least one coumn must be selected. Use 'Select all' to include all columns. |
|
Show Conversions |
Required Specify whether or not base conversions are returned. |
{True, False} Default Value: False |
Show Events |
Required Specify whether or not post-conversion events are returned. |
{True, False} Default Value: False |
Isolate conversions that were throttled |
Required Specify whether or not to isolate conversions that were throttled. |
{True, False} Default Value: False |
Isolate view-through conversions |
Required Specify whether or not to isolate view-through conversions. |
{True, False} Default Value: False |
Isolate click-through events |
Required Specify whether or not to isolate click-through events. |
{True, False} Default Value: False |
Isolate conversion and events that come from fail traffic |
Required Specify whether or not to isolate conversion and events that come from fail traffic. |
{True, False} Default Value: 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.