- Getting started
- Account management
- Security
- Destinations
- Integrations
- SaaS
- Overview
- 3PL Central
- ActiveCampaign
- AdRoll
- Amplitude
- AppsFlyer
- Asana
- Autopilot
- BigCommerce
- Braintree
- Bronto
- Campaign Manager
- Campaign Monitor
- Chargebee
- Chargify
- CircleCI
- Close.io
- Club Speed
- Codat
- COVID-19 Public Data
- Crossbeam
- Darksky
- Deputy
- Desk
- Dixa
- Doorbell.io
- eBay
- Eloqua
- Facebook Ads
- Freshdesk
- Front
- FullStory
- GitHub
- GitLab
- Google Ads
- Google Ads (AdWords)
- Google Analytics
- Google Analytics (AdWords)
- Google Analytics 360
- Google Analytics 4
- Google ECommerce
- Google Search Console
- Google Sheets
- Harvest
- Harvest Forecast
- Heap
- Help Scout
- HubSpot
- iLEVEL
- Impact
- Intacct
- Intercom
- Invoiced
- Iterable
- JIRA
- Klaviyo
- Kustomer
- Lever
- LinkedIn Ads
- Listrak
- LivePerson
- Looker
- LookML
- MailChimp
- Mailshake
- Mambu
- Marketo
- Microsoft Advertising
- Microsoft Teams
- Mixpanel
- NetSuite
- NetSuite Suite Analytics
- Onfleet
- Outbrain
- Outreach
- Pardot
- Pendo
- Pepperjam
- Pipedrive
- Quick Base
- QuickBooks
- Recharge
- Recurly
- Referral SaaSquatch
- Revinate
- RingCentral
- SaaSOptics
- Sailthru
- Salesforce
- Salesforce Marketing Cloud
- Selligent
- SendGrid Core
- ShipHero
- Shippo
- Shopify
- Slack
- Snapchat Ads
- Square
- Stripe
- SurveyMonkey
- Taboola
- TikTok Ads
- Toggl
- Trello
- Twilio
- Twitter Ads
- Typeform
- UJET
- Urban Airship
- UserVoice
- Wootric
- Workday RaaS
- Xero
- Yotpo
- Zendesk Chat
- Zendesk Support
- Zoom
- Zuora
- Databases
- Overview
- Amazon Aurora MySQL RDS
- Amazon Aurora PostgreSQL RDS
- Amazon DynamoDB
- Amazon Microsoft SQL Server RDS
- Amazon MySQL RDS
- Amazon Oracle RDS
- Amazon PostgreSQL RDS
- Amazon S3 CSV
- Google CloudSQL MySQL
- Google CloudSQL PostgreSQL
- Heroku
- Magento
- MariaDB
- Microsoft Azure MySQL
- Microsoft Azure SQL Database
- Microsoft SQL Server
- MongoDB
- MongoDB Atlas
- MySQL
- Oracle
- PostgreSQL
- Responsys
- SFTP
- Webhooks
- All integrations
- Connection cloning
- Connect other data sources
- SaaS
- Extracting data
- Loading data
- Analysis tools
- Troubleshooting
- Developers
- Changelog
Get started with a free trial today
Already have an account? Sign in
Pepperjam (v1)
Pepperjam is currently in beta. The info in this guide is subject to change.
This integration is powered bySinger's Pepperjam tap. For support,visit the GitHub repo orjoin the Singer Slack.
Pepperjam integration summary
Stitch’s Pepperjam integration replicates data using thePepperjam Advertiser API v20120402. Refer to theSchema section for a list of objects available for replication.
Pepperjam feature snapshot
A high-level look at Stitch's Pepperjam (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status | Beta | Supported by | |
| Stitch plan | Standard | API availability | Available |
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
| Anchor Scheduling | Supported | Advanced Scheduling | Supported |
| Table-level reset | Unsupported | Configurable Replication Methods | Unsupported |
| DATA SELECTION | |||
| Table selection | Supported | Column selection | Supported |
| Select all | Supported | ||
| TRANSPARENCY | |||
| Extraction Logs | Supported | Loading Reports | Supported |
Connecting Pepperjam
Step 1: Obtain your API key
- Login to your Pepperjam account.
- In theDeveloper Kit menu, clickAPI Keys.
- ClickGenerate New Key.
- Your API key will display.
Keep this page open - you’ll need it to complete the next step.
Step 2: Add Pepperjam as a Stitch data source
- Sign into your Stitch account.
On the Stitch Dashboard page, click theAdd Integration button.
Click thePepperjam icon.
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Pepperjam” would create a schema called
stitch_pepperjamin the destination.Note: Schema names cannot be changed after you save the integration.- In theAPI Key field, paste the API key you obtained instep 1.
Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Pepperjam integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Pepperjam’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.
Step 4: Create a replication schedule
In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Pepperjam integrations support the following replication scheduling methods:
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 5: Set objects to replicate
The last step is to select the tables and columns you want to replicate.Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For Pepperjam integrations, you can select:
Individual tables and columns
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’sTables to Replicate tab, locate a table you want to replicate.
To track a table, click thecheckbox next to the table’s name. A blue checkmark means the table is set to replicate.
To track a column, click thecheckbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click theFinalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
Click theTables to Replicate tab.
- In the list of tables, click the box next to theTable Names column.
In the menu that displays, clickTrack all Tables and Fields:
- Click theFinalize Your Selections button at the bottom of the page to save your data selections.
Initial and historical replication jobs
After you finish setting up Pepperjam, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to theAnchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Pepperjam replication
Attribution windows and data extraction
Every time Stitch runs a replication job for Pepperjam, the last 28-30 days’ worth of data will be replicated for the following tables:
Stitch replicates data in this way to account for updates made to existing records within an attribution window, thus ensuring you won’t make decisions based on stale (or false) data. As a result, you may see a higher number of replicated rows than what’s being generated in Pepperjam.
Setting the Replication Frequency to a higher frequency - like 30 minutes - can result in re-replicating recent data and contribute to greater row usage. Replicating fewer tables or selecting a lower frequency can help keep your row count low.
In the sections below are examples of how attribution windows impact how Stitch extracts data during historical and ongoing replication jobs.
For historical and full re-replications of Pepperjam data, Stitch will query for and extract data newer than or equal to the date defined in theStart Date field in the Integration Settings page.
TheStart Date, in conjunction with theAttribution Window, defines the minimum date Stitch should query for when extracting historical data. This is calculated as:
Start Date - Attribution Window = Minimum Extraction Date
Example
During the initial set up, theStart Date field is set toJuly 3, 2017, or2017-07-03 00:00:00.
To account for the Attribution Window, Stitch would calculate theMinimum Extraction Date value as:2017-07-03 00:00:00 - 28-30 days = 2017-06-03 00:00:00
If you were to write a SQL query using this date for thetransaction_details table, it might look like this:
SELECT*FROMpepperjam.transaction_detailsWHEREsale_date>='2017-06-03 00:00:00'/* Min. Extraction Date */ORDERBYsale_dateFor ongoing replication jobs, Stitch will query for and extract data using the last saved maximum value in the table’s Replication Key column and the Attribution Window for the table.
Note: This applies to every replication job that takes place after the historical replication job.
Example
The last maximum saved Replication Key value for thetransaction_details table is2017-10-01 00:00:00.
To account for the Attribution Window of 28-30 days, we’d subtract this from the last maximum saved Replication Key value:
2017-10-01 00:00:00 - 28-30 days = 2017-09-01 00:00:00
In this case, Stitch would query for and extract data that is newer than or equal to2017-09-01 00:00:00 and older than or equal to2017-10-01 00:00:00.
If this were a SQL query, it might look like this:
SELECT*FROMtransaction_detailsWHEREsale_date>='2017-09-01 00:00:00'/* max Replication Key value - Attribution Window */ANDsale_date<='2017-10-01 00:00:00'/* max Replication Key value from previous job */ORDERBYsale_datePepperjam table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is forversion 1 of this integration.
This is the latest version of the Pepperjam integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs >customers), while case is maintained in PostgreSQL destinations (CusTomERs >CusTomERs). Refer to theLoading Guide for your destination for more info.
creative_advanced
Thecreative_advanced table contains information about advanced link creatives in your Pepperjam account.
Key-based Incremental | |
Primary Key | id |
Replication Key | modified |
| Useful links |
| Join creative_advanced with | on |
|---|---|
| creative_banner | creative_advanced.private_affiliates.affiliate_id = creative_banner.private_affiliates.affiliate_id creative_advanced.promotions.id = creative_banner.promotions.id |
| creative_coupon | creative_advanced.private_affiliates.affiliate_id = creative_coupon.private_affiliates.affiliate_id creative_advanced.promotions.id = creative_coupon.promotions.id |
| creative_text | creative_advanced.private_affiliates.affiliate_id = creative_text.private_affiliates.affiliate_id creative_advanced.promotions.id = creative_text.promotions.id |
| creative_promotion | creative_advanced.promotions.id = creative_promotion.id |
code STRING | |||
created DATE-TIME | |||
description STRING | |||
end_date DATE-TIME | |||
flash_url STRING | |||
id INTEGER | |||
modified DATE-TIME | |||
name STRING | |||
personalized INTEGER | |||
private INTEGER | |||
private_affiliates ARRAY
| |||
promotions ARRAY
| |||
start_date DATE-TIME | |||
status STRING | |||
sub_type STRING | |||
supression_url STRING | |||
type STRING | |||
verified STRING | |||
view_date DATE-TIME |
creative_banner
Thecreative_banner table contains information about banner creatives in your Pepperjam account.
Key-based Incremental | |
Primary Key | id |
Replication Key | modified |
| Useful links |
| Join creative_banner with | on |
|---|---|
| creative_advanced | creative_banner.private_affiliates.affiliate_id = creative_advanced.private_affiliates.affiliate_id creative_banner.promotions.id = creative_advanced.promotions.id |
| creative_coupon | creative_banner.private_affiliates.affiliate_id = creative_coupon.private_affiliates.affiliate_id creative_banner.promotions.id = creative_coupon.promotions.id |
| creative_text | creative_banner.private_affiliates.affiliate_id = creative_text.private_affiliates.affiliate_id creative_banner.promotions.id = creative_text.promotions.id |
| creative_promotion | creative_banner.promotions.id = creative_promotion.id |
allow_deep_link INTEGER | |||
alt_text STRING | |||
banner_url STRING | |||
created DATE-TIME | |||
description STRING | |||
destination_url STRING | |||
end_date DATE-TIME | |||
height INTEGER | |||
id INTEGER | |||
modified DATE-TIME | |||
name STRING | |||
private INTEGER | |||
private_affiliates ARRAY
| |||
promotions ARRAY
| |||
start_date DATE-TIME | |||
status STRING | |||
type STRING | |||
view_date DATE-TIME | |||
width INTEGER |
creative_coupon
Thecreative_coupon table contains information about coupon creatives in your Pepperjam account.
Key-based Incremental | |
Primary Key | id |
Replication Key | modified |
| Useful links |
| Join creative_coupon with | on |
|---|---|
| creative_advanced | creative_coupon.private_affiliates.affiliate_id = creative_advanced.private_affiliates.affiliate_id creative_coupon.promotions.id = creative_advanced.promotions.id |
| creative_banner | creative_coupon.private_affiliates.affiliate_id = creative_banner.private_affiliates.affiliate_id creative_coupon.promotions.id = creative_banner.promotions.id |
| creative_text | creative_coupon.private_affiliates.affiliate_id = creative_text.private_affiliates.affiliate_id creative_coupon.promotions.id = creative_text.promotions.id |
| creative_promotion | creative_coupon.promotions.id = creative_promotion.id |
coupon_code STRING | |||
created DATE-TIME | |||
description STRING | |||
end_date DATE-TIME | |||
id INTEGER | |||
modified DATE-TIME | |||
name STRING | |||
personalized INTEGER | |||
private INTEGER | |||
private_affiliates ARRAY
| |||
promotions ARRAY
| |||
start_date DATE-TIME | |||
status STRING | |||
type STRING | |||
url STRING | |||
view_date DATE-TIME |
creative_generic
Thecreative_generic table contains information about generic link creatives in your Pepperjam account.
Key-based Incremental | |
Primary Key | type |
Replication Key | modified |
| Useful links |
| Join creative_generic with | on |
|---|---|
| creative_performance | creative_generic.type = creative_performance.creative_type |
| creative_performance_by_publisher | creative_generic.type = creative_performance_by_publisher.creative_type |
allow_deep_link INTEGER |
modified DATE-TIME |
type STRING |
url STRING |
creative_performance
Thecreative_performance table contains information about your Pepperjam creatives’ performance within a -day time frame from the date of the last table replication.
Note: During every replication job, Stitch will replicate the last days’ worth of data for this table. Refer to theAttribution windows and data extraction section for more info.
Key-based Incremental | |
Primary Keys | creative_id creative_type date |
Replication Key | datetime |
| Useful links |
| Join creative_performance with | on |
|---|---|
| creative_performance_by_publisher | creative_performance.creative_id = creative_performance_by_publisher.creative_id creative_performance.group_id = creative_performance_by_publisher.group_id creative_performance.creative_type = creative_performance_by_publisher.creative_type |
| transaction_details | creative_performance.creative_id = transaction_details.creative_id creative_performance.group_id = transaction_details.group_id |
| group | creative_performance.group_id = group.id |
| group_member | creative_performance.group_id = group_member.group_id |
| publisher | creative_performance.group_id = publisher.group.id |
| publisher_performance | creative_performance.group_id = publisher_performance.group_id |
| transaction_history | creative_performance.group_id = transaction_history.group_id |
| creative_generic | creative_performance.creative_type = creative_generic.type |
affiliate_usage INTEGER |
click_through_rate NUMBER |
clicks INTEGER |
commission NUMBER |
creative_id INTEGER |
creative_name STRING |
creative_type STRING |
date DATE |
datetime DATE-TIME |
earnings_per_click NUMBER |
group_id INTEGER |
impressions INTEGER |
items INTEGER |
sales NUMBER |
transactions INTEGER |
creative_performance_by_publisher
Thecreative_performance_by_publisher table contains information about your Pepperjam creatives’ performance, per publisher, within a -day time frame from the date of the last table replication.
Note: During every replication job, Stitch will replicate the last days’ worth of data for this table. Refer to theAttribution windows and data extraction section for more info.
Key-based Incremental | |
Primary Keys | creative_id creative_type date publisher_id |
Replication Key | datetime |
| Useful links |
| Join creative_performance_by_publisher with | on |
|---|---|
| creative_performance | creative_performance_by_publisher.creative_id = creative_performance.creative_id creative_performance_by_publisher.group_id = creative_performance.group_id creative_performance_by_publisher.creative_type = creative_performance.creative_type |
| transaction_details | creative_performance_by_publisher.creative_id = transaction_details.creative_id creative_performance_by_publisher.group_id = transaction_details.group_id creative_performance_by_publisher.publisher_id = transaction_details.publisher_id |
| group | creative_performance_by_publisher.group_id = group.id |
| group_member | creative_performance_by_publisher.group_id = group_member.group_id |
| publisher | creative_performance_by_publisher.group_id = publisher.group.id creative_performance_by_publisher.publisher_id = publisher.id |
| publisher_performance | creative_performance_by_publisher.group_id = publisher_performance.group_id creative_performance_by_publisher.publisher_id = publisher_performance.publisher_id |
| transaction_history | creative_performance_by_publisher.group_id = transaction_history.group_id creative_performance_by_publisher.publisher_id = transaction_history.publisher_id |
| creative_generic | creative_performance_by_publisher.creative_type = creative_generic.type |
affiliate_usage INTEGER |
click_through_rate NUMBER |
clicks INTEGER |
commission NUMBER |
creative_id INTEGER |
creative_name STRING |
creative_type STRING |
date DATE |
datetime DATE-TIME |
earnings_per_click NUMBER |
group_id INTEGER |
impressions INTEGER |
items INTEGER |
publisher STRING |
publisher_id INTEGER |
sales NUMBER |
transactions INTEGER |
creative_product
Thecreative_product table contains information about product creatives in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
age_range STRING |
artist STRING |
aspect_ratio STRING |
author STRING |
battery_life STRING |
binding STRING |
buy_url STRING |
category_network STRING |
category_program STRING |
color STRING |
color_output STRING |
condition STRING |
description_long STRING |
description_short STRING |
director STRING |
discontinued STRING |
display_type STRING |
edition STRING |
expiration_date STRING |
features STRING |
focus_type STRING |
functions STRING |
genre STRING |
heel_height STRING |
height STRING |
id INTEGER |
image_thumb_url STRING |
image_url STRING |
in_stock STRING |
installation STRING |
isbn STRING |
keywords STRING |
length STRING |
load_type STRING |
location STRING |
made_in STRING |
manufacturer STRING |
material STRING |
megapixels STRING |
memory_capacity STRING |
memory_card_slot STRING |
memory_type STRING |
model_number STRING |
mpn STRING |
name STRING |
occasion STRING |
operating_system STRING |
optical_drive STRING |
pages INTEGER |
payment_accepted STRING |
payment_notes STRING |
platform STRING |
price NUMBER |
price_retail NUMBER |
price_sale NUMBER |
price_shipping NUMBER |
processor STRING |
product_format STRING |
publisher STRING |
quantity_in_stock INTEGER |
rating STRING |
recommended_usage STRING |
resolution STRING |
screen_size STRING |
shipping_method STRING |
shoe_size STRING |
shoe_width STRING |
size STRING |
sku STRING |
staring STRING |
style STRING |
tech_spec_url STRING |
tracks INTEGER |
upc STRING |
weight STRING |
width STRING |
wireless_interface STRING |
year STRING |
zoom STRING |
creative_promotion
Thecreative_promotion table contains information about promotion creatives in your Pepperjam name account.
Full Table | |
Primary Key | id |
| Useful links |
| Join creative_promotion with | on |
|---|---|
| creative_advanced | creative_promotion.id = creative_advanced.promotions.id |
| creative_banner | creative_promotion.id = creative_banner.promotions.id |
| creative_coupon | creative_promotion.id = creative_coupon.promotions.id |
| creative_text | creative_promotion.id = creative_text.promotions.id |
id STRING |
name STRING |
creative_text
The creative_text table contains information about text creatives in your Pepperjam account.
Key-based Incremental | |
Primary Key | id |
Replication Key | modified |
| Useful links |
| Join creative_text with | on |
|---|---|
| creative_advanced | creative_text.private_affiliates.affiliate_id = creative_advanced.private_affiliates.affiliate_id creative_text.promotions.id = creative_advanced.promotions.id |
| creative_banner | creative_text.private_affiliates.affiliate_id = creative_banner.private_affiliates.affiliate_id creative_text.promotions.id = creative_banner.promotions.id |
| creative_coupon | creative_text.private_affiliates.affiliate_id = creative_coupon.private_affiliates.affiliate_id creative_text.promotions.id = creative_coupon.promotions.id |
| creative_promotion | creative_text.promotions.id = creative_promotion.id |
allow_deep_link INTEGER | |||
created DATE-TIME | |||
description STRING | |||
end_date DATE-TIME | |||
id INTEGER | |||
link_anchor_text STRING | |||
modified DATE-TIME | |||
private INTEGER | |||
private_affiliates ARRAY
| |||
promotions ARRAY
| |||
start_date DATE-TIME | |||
status STRING | |||
type STRING | |||
url STRING | |||
view_date DATE-TIME |
group
Thegroup table contains information about groups in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
| Join group with | on |
|---|---|
| creative_performance | group.id = creative_performance.group_id |
| creative_performance_by_publisher | group.id = creative_performance_by_publisher.group_id |
| group_member | group.id = group_member.group_id |
| publisher | group.id = publisher.group.id |
| publisher_performance | group.id = publisher_performance.group_id |
| transaction_details | group.id = transaction_details.group_id |
| transaction_history | group.id = transaction_history.group_id |
assigned_publishers INTEGER |
id INTEGER |
name STRING |
group_member
Thegroup_member table contains information about members within groups in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
| Join group_member with | on |
|---|---|
| creative_performance | group_member.group_id = creative_performance.group_id |
| creative_performance_by_publisher | group_member.group_id = creative_performance_by_publisher.group_id |
| group | group_member.group_id = group.id |
| publisher | group_member.group_id = publisher.group.id |
| publisher_performance | group_member.group_id = publisher_performance.group_id |
| transaction_details | group_member.group_id = transaction_details.group_id |
| transaction_history | group_member.group_id = transaction_history.group_id |
default STRING |
group_id INTEGER |
id INTEGER |
name STRING |
product_count INTEGER |
itemized_list
Theitemized_list table contains information about your itemized lists in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
| Join itemized_list with | on |
|---|---|
| itemized_list_product | itemized_list.id = itemized_list_product.list_id |
default STRING |
id INTEGER |
name STRING |
product_count INTEGER |
itemized_list_product
Theitemized_list_product table contains information about products within your itemized lists in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
| Join itemized_list_product with | on |
|---|---|
| itemized_list | itemized_list_product.list_id = itemized_list.id |
id STRING |
list_id INTEGER |
name STRING |
publisher
Thepublisher table contains information about the publishers, the publishers’ status, and the publishers’ term in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
| Join publisher with | on |
|---|---|
| creative_performance | publisher.group.id = creative_performance.group_id |
| creative_performance_by_publisher | publisher.group.id = creative_performance_by_publisher.group_id publisher.id = creative_performance_by_publisher.publisher_id |
| group | publisher.group.id = group.id |
| group_member | publisher.group.id = group_member.group_id |
| publisher_performance | publisher.group.id = publisher_performance.group_id publisher.id = publisher_performance.publisher_id |
| transaction_details | publisher.group.id = transaction_details.group_id publisher.id = transaction_details.publisher_id |
| transaction_history | publisher.group.id = transaction_history.group_id publisher.id = transaction_history.publisher_id |
| term | publisher.term.id = term.id |
category ARRAY
| ||
company STRING | ||
country STRING | ||
first_name STRING | ||
group ARRAY
| ||
id INTEGER | ||
join_date DATE-TIME | ||
last_name STRING | ||
primary_promo_method STRING | ||
promotional_method ARRAY
| ||
request_date DATE-TIME | ||
state STRING | ||
status STRING | ||
term ARRAY
| ||
transparency INTEGER | ||
website STRING |
publisher_performance
Thepublisher_performance table contains information about publishers’ performance within a -day time frame from the date of the last table replication.
Note: During every replication job, Stitch will replicate the last days’ worth of data for this table. Refer to theAttribution windows and data extraction section for more info.
Key-based Incremental | |
Primary Keys | date publisher_id |
Replication Key | datetime |
| Useful links |
| Join publisher_performance with | on |
|---|---|
| creative_performance | publisher_performance.group_id = creative_performance.group_id |
| creative_performance_by_publisher | publisher_performance.group_id = creative_performance_by_publisher.group_id publisher_performance.publisher_id = creative_performance_by_publisher.publisher_id |
| group | publisher_performance.group_id = group.id |
| group_member | publisher_performance.group_id = group_member.group_id |
| publisher | publisher_performance.group_id = publisher.group.id publisher_performance.publisher_id = publisher.id |
| transaction_details | publisher_performance.group_id = transaction_details.group_id publisher_performance.publisher_id = transaction_details.publisher_id |
| transaction_history | publisher_performance.group_id = transaction_history.group_id publisher_performance.publisher_id = transaction_history.publisher_id |
bonus_amount NUMBER |
clicks INTEGER |
company STRING |
date DATE |
datetime DATE-TIME |
earnings_per_click NUMBER |
group_id INTEGER |
impressions INTEGER |
leads INTEGER |
publisher STRING |
publisher_bonus NUMBER |
publisher_commission NUMBER |
publisher_id INTEGER |
publisher_type STRING |
sale_lead_amount NUMBER |
sales INTEGER |
site_bonus NUMBER |
site_commission NUMBER |
state STRING |
total_commission NUMBER |
website STRING |
term
Theterm table contains information about the terms for your program in your Pepperjam account.
Full Table | |
Primary Key | id |
| Useful links |
| Join term with | on |
|---|---|
| publisher | term.id = publisher.term.id |
cookie_duration STRING |
created DATE |
default STRING |
id INTEGER |
name STRING |
transaction_details
The transaction_details table contains all publisher transaction details, within a -day time frame from the date of the last table replication.
Note: During every replication job, Stitch will replicate the last days’ worth of data for this table. Refer to theAttribution windows and data extraction section for more info.
Key-based Incremental | |
Primary Key | transaction_id |
Replication Key | sale_date |
| Useful links |
| Join transaction_details with | on |
|---|---|
| creative_performance | transaction_details.creative_id = creative_performance.creative_id transaction_details.group_id = creative_performance.group_id |
| creative_performance_by_publisher | transaction_details.creative_id = creative_performance_by_publisher.creative_id transaction_details.group_id = creative_performance_by_publisher.group_id transaction_details.publisher_id = creative_performance_by_publisher.publisher_id |
| group | transaction_details.group_id = group.id |
| group_member | transaction_details.group_id = group_member.group_id |
| publisher | transaction_details.group_id = publisher.group.id transaction_details.publisher_id = publisher.id |
| publisher_performance | transaction_details.group_id = publisher_performance.group_id transaction_details.publisher_id = publisher_performance.publisher_id |
| transaction_history | transaction_details.group_id = transaction_history.group_id transaction_details.order_id = transaction_history.order_id transaction_details.publisher_id = transaction_history.publisher_id transaction_details.transaction_id = transaction_history.transaction_id |
click_id STRING |
commission NUMBER |
commission_publisher NUMBER |
commission_site NUMBER |
company STRING |
coupons STRING |
creative_id STRING |
device_type STRING |
group_id INTEGER |
link_type STRING |
new_to_file STRING |
order_id STRING |
publisher STRING |
publisher_id INTEGER |
publisher_type STRING |
sale_amount NUMBER |
sale_date DATE-TIME |
status STRING |
transaction_id INTEGER |
transaction_type STRING |
transaction_history
The transaction_history table contains all historical publisher transactions, within a -day time frame from the date of the last table replication.
Note: During every replication job, Stitch will replicate the last days’ worth of data for this table.
Key-based Incremental | |
Primary Keys | transaction_id process_date sale_date |
Replication Key | sale_date |
| Useful links |
| Join transaction_history with | on |
|---|---|
| creative_performance | transaction_history.group_id = creative_performance.group_id |
| creative_performance_by_publisher | transaction_history.group_id = creative_performance_by_publisher.group_id transaction_history.publisher_id = creative_performance_by_publisher.publisher_id |
| group | transaction_history.group_id = group.id |
| group_member | transaction_history.group_id = group_member.group_id |
| publisher | transaction_history.group_id = publisher.group.id transaction_history.publisher_id = publisher.id |
| publisher_performance | transaction_history.group_id = publisher_performance.group_id transaction_history.publisher_id = publisher_performance.publisher_id |
| transaction_details | transaction_history.group_id = transaction_details.group_id transaction_history.order_id = transaction_details.order_id transaction_history.publisher_id = transaction_details.publisher_id transaction_history.transaction_id = transaction_details.transaction_id |
commission NUMBER |
company STRING |
group_id INTEGER |
item_id STRING |
link_type STRING |
order_id STRING |
process_date DATE-TIME |
publisher STRING |
publisher_commission NUMBER |
publisher_id INTEGER |
publisher_type STRING |
revision STRING |
sale_amount NUMBER |
sale_date DATE-TIME |
site_commission NUMBER |
status STRING |
transaction_id INTEGER |
transaction_type STRING |
website_url STRING |
| Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.