Marketo

Data Replication

Default Pipeline Frequency	Minimum Pipeline Frequency	Maximum Pipeline Frequency	Custom Frequency Range (Hrs)
3 Hrs	3 Hrs	48 Hrs	3-48

Note: The custom frequency must be set in hours, as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

Hevo ingests the data from Marketo as follows:

• Historical Data: In the first run of the Pipeline, Hevo ingests the data of the past one year, a month at a time, for the selected objects using the Recent Data First approach.

• Incremental Data: Once the historical load is complete, all new records are synchronized with your Destination as per the Pipeline frequency.

• Data Refresh: The data for the past three months is ingested on every run to ensure that your data is up to date and any data freshness issues are overcome.
  

Refer to the table below for the type of data that is fetched for each object.

Data Type	Object Names	Schedule	Additional Information
Historical	Activities	During the first run of the Pipeline
Incremental	Activities, Activity Types, Campaigns, Leads, Programs	During each run of the Pipeline	For the Campaigns object, data for the past 12 months is fetched on the first run.
Refresh Data	Leads	Every 24 hours post-completion of ingestion	Ensures that leads, opportunity, opportunity roles, and salespersons data is up to date.

Note: The time taken for the Historical data load is determined by the amount of data and processing time for the ingestion from Marketo.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

---

Data Model

The following is the list of tables (objects) and their primary keys that are created at the Destination when you run the Pipeline.

If you have selected AutoMapping, Hevo creates the tables in the Destination automatically. Else, you must manually create and map the tables. See sample image here:

Note: The table names are written in small case, except for the Snowflake data warehouse tables which are written in uppercase.

Table	Primary Key	Parent Object	Bulk API
activity_types (Custom activity types as well as Marketo-provided activity types are loaded into the same table.)	ID	NA	NA
campaigns	ID	NA	NA
lead_activities	marketoGUID	NA	Bulk activity extract
leads	leadId	NA	Bulk lead extract
opportunity	marketoGUID	lead_activities	NA
oppportunity_role	marketoGUID	lead_activities	NA
program	ID	NA	NA
program_members	ID	program	Bulk program member extract
sales_persons	ID	lead_activities	NA
smart_list	ID	campaigns	NA

Linked objects: Wherever there is a dependency between objects, the job is created for only the higher-level object. The same job fetches the data for the linked object also. However, you can see separate tables in Schema Mapper for each such linked object. For example, when you fetch Campaigns data, Smart List data is automatically fetched. So, while you see the Smart List table in Schema Mapper, there is no job created by this name.

---