Synchronize user data using automation -

The Sync to Third Party Automation Action should be used to push Contact Data from the platform to an API listener page on your server. You can in turn insert this data into your database or to your CRM, given it has its own api.nnThis listener is a web page or web application you create on your server that is always active and has code that allows it to accept and verify “contact” data sent from the platform, This listener then invokes backend services on your server, based on the information received.nnYou have 3 options to sync your data:nn1- Retargeting Audience: Facebook Ads and Google Adwords.nnChoose an audience to sync your contact to.nnnn2- Native Integration: Salesforce, Hubspot, etc.nnChoose one of the sync that you have already created in one of the connectors. Please note that the sync type should be Automation (Generates URL).nnnn3- Webhook: Your own URL.nnAdd your Webhook URL, choose what to sync, the sending method and the Data content type.nnn

How it works

Create a private file on your server that is not publicly accessible to front-end users. The custom listener code will be added to this file (more explanation below).

On the automation action, choose Synch Contact to Third Party, choose which marketing data to synchronize and insert the path to the file created in step 1.n

The platform will automatically send the marketing data to you each time a contact matches the automation rules specified.

The platform sends a FORM POST containing contact information appended to the URL.

The API listener (code sample included below) detects and processes the data.

The API listener page must contain a custom script that waits for the messages, and then passes them to various backend applications for processing.

List of available marketing data

nnThere are two ways to sync the data from the platform to the third party app.n

Using GET as in this example: https://www.example.com/?param1=[#SHORTCODE-1#]&param2=[#SHORTCODE_2#]&… where [#…#] are the custom fields shortcodes from the list you are targeting within the journey. These shortcodes will hold the values of the contact that reached that action, within the journey. The URL would be your receiving end of the API. Note you can use our shortcode library to manipulate the shortcodes, ex: [#PROPER EMAIL/2#] and there are no limits on the number of fields you can pass.

Using POST request in the following order:n

Arrayn(n    [transactionid] => 123456789n    [contact] => Array()n    [fields] => Array()n    [campaigns-opened] => Array()n    [links-clicked] => Array()n    [pages-visited] => Array()n    [automation-triggered] => Array()n    [goals-reached] => Array()n    [webhooks-triggered] => Array()n    [lead-score] => Array()n    [lead-status] => Array()n)

Basic Information: ‘contact’

nnThis field contains basic contact information such id, email address and phone number as Array:n

Arrayn(n    [id] => Contact's IDn    [email] => Contact's E-mail Addressn    [phone] => Contact's Phonen    [profile_url] => Contact's Profile Pagen)

Custom Fields: ‘fields’

nnThis field contains an array list of arrays of the custom fields for the contact:n

Arrayn(n    [id] => Field IDn    [name] => Field namen    [value] => Contact's field valuen)

Email Campaigns Open: ‘campaigns-opened’

nnThis field contains an array list of arrays of the campaigns opened by the contact:n

Arrayn(n    [id] => Campaign IDn    [name] => Campaign namen    [open_date] => Contact's open campaign date/timen)

Links Clicked: ‘links-clicked’

nnThis field contains an array list of arrays of the links clicked by the contact:n

Arrayn(n    [url] => Link urln    [clicks] => Contact's total clicksn)

Pages Visited: ‘pages-visited’

nnThis field contains an array list of arrays of the pages visited by the contact:n

Arrayn(n    [page] => Page urln    [visit_date] => Contact's page visit date/timen)

Automation Triggered: ‘automation-triggered’

nnThis field contains an array list of arrays of the automation workflows triggered by the contact:n

Arrayn(n    [id] => Automation IDn    [name] => Automation namen    [trigger_date] => Contact's automation triggered date/timen)

Goals Reached: ‘goals-reached’

nnThis field contains an array list of arrays of the goals reached by the contact:n

Arrayn(n    [id] => Goal IDn    [name] => Goal namen    [reach_date] => Contact's goal reached date/timen)

Webhooks Triggered: ‘webhooks-triggered’

nnThis field contains an array list of arrays of the webhooks triggered by the contact:n

Arrayn(n    [id] => Webhook IDn    [name] => Webhook namen    [trigger_date] => Contact's webhook triggered date/timen)

Lead Score: ‘lead-score’

nnThis field contains an array list of arrays of the lead scoring reached by the contact:n

Arrayn(n    [id] => Score IDn    [name] => Score namen    [score] => Score valuen    [score_date] => Contact's score triggered date/timen)

Lead Status: ‘lead-status’

nnThis field contains an array list of arrays of the lead status reached by the contact:n

Arrayn(n    [score] => Contact's total scoren    [label] => Contact's score labeln)n

Update contact from response

nYou have the option to update your contact info based on the API response.nnTurn on the Update contact from response option and choose the key response you need to map to a contact field.nnn

[lore_button label=”Get Started” link=”app.aoaassociates.com/Login” size=”regular” style=”default”]