Act-On - Post to Webform - Add Lead

A form is published in Act-On to receive your ion data. Next a field mapping is completed in ion to define which ion fields should be exported and where that data should be submitted in your Act-On form. You can configure your integration to post to a single (“master”) Act-On form for processing ion leads, or leverage a dynamic destination to support posting to multiple Act-On forms from a single ion integration.

When the integration runs, data collected in ion is re-posted to the designated Act-On form.

Step 1

Fieldmapping

Setup the Fieldmapping based on the Worksheet provided by the client. And adjust the form on the right to collect all Fields.

Example: Act-On - Post to web form - Add Lead

Recommendation: In order to keep Fieldmappings as flexible as possible only make the e-mail address required. This tends to allow the fieldmapping to be reused with a lot of variations of form in creative.

In order to dispel the concerns of the client. Fields can still be made required in the form in the creative to make sure all data they want is collected.

Step 2

Integration

Setup the Integration using the Fieldmapping created in the previous step. Adding the Form URL that the client has generated. (Act-on Helpdesk Page)

Example: Act-On - Post to web form - Add Lead

Advanced:

1. Make the Act-On endpoint URL dynamic, supported by a form rule that saves the respective URL

In the Ion integration, replace the Form URL a dynamic placeholder, like so: {{FormURL}}

Above the form-level rule action that runs the integration, save the FormURL value:

Condition: No conditions required

Action: Save data - FormURL = paste FormURL value here

This allows the client to use different forms with the same integration.

Step 3

Creative

Add the integration trigger. This is usually the submit button on the form. But can be placed anywhere that allows you to add Rules to an action or a Page.

Example: Act-On - Post to web form - Add Lead - Submit Button

Recommendation: Add the Mark to re-run integration action before the Run integration action

Note

The following step is optional and only need to be followed if Act-On tracking should be applied to the creative.

Step 4

Tracking

Guide the client to provide the Act-On tracking code (Act-On Documentation)
Add the Code as a Library Script to the console
Apply the Library Script to appropriate level. usually the creative level so it doesn't need to be added to every page of the creative manually.

Form Headline Goes Here

First Name *

Last Name *

Email *