Skip to main content
Sign in

Using HTTP Raw

Vorpahl
  • Updated

Relevant to: Demand Acceleration Platform | Content Syndication | Webinar Integrations | Social Integrations

Use a HTTP Raw integration to create almost any kind of post out to your Marketing Automation/CRM system. This method is ideal if:

  • The Demand Acceleration Platform does not offer a native integration with your system.
  • You need to use a language or format that is different from URL Encode, such as XML or JSON. If you can use a URL Encode, you are advised to set-up an integration with an Outbound Form.

 

 

Adding a HTTP Raw Integration to a Campaign/Source

1. In the Demand Acceleration Platform, go to your Campaign/Source and navigate to the Integrations tab. Click the Add Integration button.

dap-postouts-setupmarketo-01.png

 

2. You will be presented with the Add Integration modal. 

dap-postouts-httpraw-01.png

 

Here there are two options:

  • Option 1: Create a new Campaign/Source integration – Start from scratch! This will essentially create a default integration with the fields you created on the Fields tab of the Campaign or Source and their corresponding tokens will auto-populate in string format. You will need to review and manually adjust the field names and values within the Body according to your system needs. 
    • This option is most helpful when:
      • You or your team are new to the Demand Acceleration Platform.
      • You haven’t built any Campaign/Sources with a similar set up.
      • You are using very few fields or unique fields within this Source (eg. in Social or Webinar Sources, which have fewer, more specific fields).
  • Option 2: Load From Existing – Start from something similar! This will make an exact copy of an existing integration from another Campaign/Source. Once loaded, changes can be made for the new Source.
    • This option is most helpful when:
      • You already have an existing integration that used similar fields and set up details (eg. existing builds from the same team, region, program).
      • You are creating multiple Sources that use the same Social or Webinar form fields.
      • You have complex routing rules that you’d like to copy and manually check the Source fields and details match.

Decide which option works best for your build; instructions for both are outlined below.

 

Option 1: Create a new Campaign/Source integration

1. In the Add Integration pop-up modal, select My HTTP from the list.

dap-postouts-httpraw-02.png

 

This is now listed as an integration with a visible tile. Proceed to Configure your HTTP Raw integration.

dap-postouts-httpraw-03.png

 

Option 2: Load From Existing

1. In the Add Integration pop-up modal, select the Load From Existing button.

dap-postouts-httpraw-04.png

 

2. You will then be presented with a list of the existing Campaign template integrations to choose from. If you wish to switch to view your Source Integrations, use the Showing Campaigns button and select Source from the dropdown.

dap-postouts-settingupeloqua-05.png

 

3. Click the desired Campaign/Source integration and select the integration from the dropdown in the Integration Name column. Then click the Load Integration button.

dap-postouts-httpraw-06.png

This will load a copy of your existing integration to the new Campaign/Source, which you can adjust accordingly.

Proceed to the Configuring Your HTTP Raw Integration section below for more details.

 

Configuring Your HTTP Raw Integration

Once an integration has been added to your Campaign/Source, you need to configure some key elements to define how lead data is sent to your Marketing Automation or CRM system.

1. To open your integration, hover over the integration tile and click the Settings icon.

dap-postouts-httpraw-07.png

2. Move through the sections below to configure your integration according to the needs of your Campaign/Source.

dap-postouts-httpraw-08.png

Field
 Description
Profile Name

Enter a name for your integration.

  • This is just to help you identify it within the Demand Acceleration Platform and can be anything you like.
  • If you will be connecting multiple instances, use a naming convention to help you distinguish them.

Method

POST

A POST method is used to send data to your Marketing Automation/CRM system - this method will create new leads.

  • The POST method is most commonly used.

PUT

A PUT method is used to send data to your Marketing Automation/CRM system - this method will create new leads and update existing leads.

GET

A GET method is used to request data from your Marketing Automation/CRM system.
URL

Paste in the URL value from your Marketing Automation/CRM system where you will be posting leads.
Headers

Enter any necessary Headers - typically, these are information such as authorization or security tokens, though this is dependant on where leads are being posted.

Body

URL Encode Request checkbox

The purpose of this checkbox is to ensure certain special characters pass into and display within your system properly.

This box may or may not need to be checked according to your Marketing Automation or CRM system.

Configure your post out string specific to your system requirements. This is where all the information you wish to post into your system will go. 

  • The fields you created on the Fields tab of the Campaign or Source and their corresponding tokens will auto-populate in string format.
  • Review and adjust the field names and values within the Body according to your system needs.
    • In the following format, you would replace the values highlighted in bold:
yourSystemFieldName={{lead.IntegrateFieldName}}
    • Example:
firstName={{lead.first_name}}
  • To add any additional fields required for posting leads to your system (ie. Integrate ID), add your system field name to the string and select the corresponding token from the list of available tokens to the right.
IntegrateID={{lead.Id}}
  • To add a static or hidden field and value, add the field name to the string and enter the value after the equal sign.
leadsource=Integrate

 

When values are combined, the body string would look like:

firstName={{lead.first_name}}
&lastName={{lead.last_name}}
&Email={{lead.email}}
&Company={{lead.company_name}}
&IntegrateID={{lead.Id}}
&leadsource=Integrate
Configuration of the Body will look different for each system.
Work with your Customer Success Manager to configure this for your requirements.

dap-postouts-httpraw-09.png

 

Testing the Integration

It's really important to test your integration before you start collecting leads. It's advisable to work closely with your Marketing Ops team for this as you will need to check that sample data is posted into your Marketing Automation or CRM system.

For instructions on testing your integration, see Testing an outbound integration.

The integration has been added to your Campaign/Source.
The next step is to test the integration.

 

 

Recommended Reading

 

For more help, get in touch with our Support Team or your Customer Success Manager.

Related articles