In 2021, Marketo disabled posts to save2 endpoint. As a result, PathFactory switched to utilizing the Marketo Form Submit API export as a way to facilitate engagement session data send from PathFactory to Marketo.

From PathFactory, there are 5 different types of engagement data that can be sent to Marketo

Session based (Highly recommend if deploying the following experiences)

Standard Experiences Session
Website Tools (WT)Session
Templated Experience (TE) Session

Activity Based (optional)

Standard Experiences
Templated Experience and Website Tools Activity

This article uses the Standard or TE Experience session based set up as an example. Other Session and Activity Based events will follow similar steps in creating the API Form Submission Exports but may have different field requirements

Step 1: Create fields in Marketo

First, you need to create new custom property fields in Marketo. You can find this configuration in Marketo’s Admin Settings > Field Management.

You will typically be sent a standard list of fields by one of our Implementation Specialists if you are currently onboarding with us. See the following recommended fields to include for a Standard or Templated Experience session based event.

Note: The full list of engagement fields is here.

Field names

Field Name	Field Value	Field Type	Description
PathFactory Experience Name	pathFactoryExperienceName	String	The name of the last PathFactory Content Experience that the contact engaged with during the session.
PathFactory Number of Assets Viewed	pathFactoryNumberofAssetsViewed	Integer	Number of unique content assets viewed during the session.
PathFactory Content Count – Threshold Met	pathFactoryContentCountMetThreshold	Integer	The number of assets for which the engagement threshold has been met while the visitor engaged with a PathFactory Content Track.
PathFactory Content Journey	pathFactoryContentJourney	Text Area	The order of assets viewed during the session, represented by their unique URL slugs.
PathFactory Content List – Threshold Met	pathFactoryContentListThresholdMet	Text Area	All the content assets viewed during the session which had their time thresholds met, represented by their unique URL slugs.
PathFactory Topic List – Threshold Met	pathFactoryTopicListThresholdMet	String	The topics for each content asset which had its time threshold met during the session.
PathFactory Funnel Stage – Threshold Met	pathFactoryFunnelStageThresholdMet	String	The funnel stage of each content asset which had its time threshold met during the session.
PathFactory Content Types List– Threshold Met	pathFactoryContentTypesListThresholdMet	Text Area	The asset type for each content asset which had its time threshold met during the session.
PathFactory Engagement Score	pathFactoryEngagementScore	Integer	Score given to the visitor for the session. Configurable based on different levels of engagement.
PathFactory External ID	pathFactoryExternalID	String	The value provided in the External ID attribute from the Content Track that was visited during the session.
PathFactory Engagement Time	pathFactoryEngagementTime	Integer	Total time the visitor spent engaging with all PathFactory content assets during the session.
PathFactory Last Viewed Content Title	pathFactoryLastViewedContentTitle	String	The public title of the last piece of content viewed in a session.
PathFactory Last Viewed Content Source URL	pathFactoryLastViewedContentSourceURL	String	The underlying URL of the last viewed asset in the session.

Note: Please use the Field Type as we have recommended.

Step 2: Create a Marketo form

Create a new Marketo form in your Marketo instance. Give the form a name that fits with your team and workflow. Common examples include Standard and Templated Experience PathFactory Forms API Sessions or Standard and Templated Experience Visitor Sessions. This form won’t be displayed to your visitors so keep the fields surfaced on the form as it could help you with testing.

Note: You may use the same Marketo form across the different types of sessions if you wish. You’ll want to include all fields created to capture PathFactory engagement data. This form won’t be displayed to your visitors, so keep the fields surfaced on the form as it could help us with testing.

Add all the fields you just created.
Add an Email field as well, which is the main unique identifier that converts the visitor.
Ensure the email field is the only required field.
When completed, select Finish and Approve and Close to save any changes.

Step 3: Set up the Form API Export in PathFactory

Login to your PathFactory instance.
Navigate to Organization Settings > Marketo Account tab.
Select + Add API Form Submission Export. A modal appears.
Complete the following fields in the modal.

Name: this name only appears in PathFactory, so choose whatever works best for you. Common examples are PathFactory Visitor Session or PathFactory Session.

Marketo Form ID: find this ID in your Marketo form embed code and paste it here. In the following example, my form ID is 1842.

Event Type: Choose Standard Experiences Session

Fire for Excluded Visitors: select this option if you want data for excluded visitors (such as both your internal employees and PathFactory employees) to be included in the data.

Step 4: Add the fields in your Forms API

Since your API is connected to your PathFactory instance, you don’t need to manually populate the fields.

Select Configure Event Fields. A modal opens.
Marketo field dropdown list
Using the Event Field and Marketo Form Field drop-downs, map the PathFactory fields to the corresponding Marketo fields. Refer to the previous list of standard field names if necessary.
Select Save. You’re all ready to go!

Additional Form Submit API Export Settings

Edit: use if you want to edit the name of your form in PathFactory.

Refresh Marketo Form Fields: use to make updated, deleted, or new fields appear in the Marketo Form Field drop-down.

Remove: use to delete the form from PathFactory.

WARNING: removal is permanent. Deleted forms cannot be retrieved. You’ll have to re-create any removed forms.

Set up notification email for export failures

The API form submission export includes call logs as well automated email notification when failed calls occur. This feature ensures you will be notified immediately if an issue occurs with this data flow, versus having to periodically check.

If the last export was successfully processed, you’ll see the last processed date and time in UTC format. If the last export was not successful, you’ll see the last attempted export date and time in UTC format, and the failure log.

To set up an email notification, navigate to Organization Settings and select the Marketo Account tab. Here you can input the email address for the notification to be sent to. You can also see the last export status within this tab.