Signal Integration with Marketo Guide

Certain Signal Connector (also called the “Certain Signal Connector: Marketo Native Integration Guide”) is a guide to using Certain Signal Connector to integrate with Marketo.

(Signal Connector also integrates with other products, including Eloqua and Salesforce via native integrations and others via Webhooks or Advanced Webhooks – see separate guides.)

This product is not included with Certain Platform by default. If you’re interested in it after reading this document, please email help@certain.com and features@certain.com, including your account name.

What is Signal Connector? How does it work?

Certain Signal Connector processes data from your events in real-time, passing it from Certain Platform to your instance of Marketo.

This real-time integration empowers sales and marketing teams to take intelligent, prompt action on the right event data.

Almost everything is set up at the account level. Signal Connector processes information from the events in your account. For event-level information, this is based on the custom tags you attach to data such as Events, Custom Registration Properties, or Registration Statuses, as explained in this guide.

Important: Signal Connector processes outbound information.

Signal Connector processes information from Certain and sends it to Marketo.

Prerequisites

Data-Flow Considerations

If so, you’ll need to apply tags to those questions: see Registration Questions.

If so, you’ll need to apply tags to those items: see Registration Status or Attendee Types.

One campaign that’s common to all events, or one campaign per event?

If one per event, you’ll need an Event Question for the Campaign ID: see Campaign ID.

Marketo Credentials

To set up a Connection in Signal Connector (see Setting up a Connection), you’ll need to know the URL you use to log in to Marketo. Your Marketo administrator will need to create an OAuth2 app in Marketo by going to Admin> Integration > LaunchPoint > New Service > Service: Custom > Create.

They then need to provide you with the following details:

Overview of Setup Steps

StepSee Page
On Certain Platform: 1. Add tags in the accountSetting up Tags
On Certain Platform: 2. Apply those tagsApplying Tags
In Certain Signal Connector: 3. Add a ConnectionAdding a Connection
In Certain Signal Connector: 4. Configure a FlowSetting up Flows

Setting up Tags

What Are Tags?

Tags are a way of identifying event-level data using labels you set at the account level.

You can then apply those tags to generic items in events. Those generic items include custom registration statuses and custom registration properties for use in Certain Signal Connector. (Tags can be used for other purposes, but this guide doesn’t cover that.)

For example, your events may have several custom registration statuses in addition to the standard ones. You can apply the same Tags to more than one status. You can also give each status its own Tag.

When you set up a Flow in Certain Signal Connector to send data to Marketo when an attendee’s Registration Status changes, you specify the tags applicable to those statuses. You specify tags instead of the statuses themselves. This means the flow can apply to any event in your account.

Setting Tags Up for an Account

1. As an Administrator, go to Account Settings > Management >Tags. 2. Enter a Name and a Label for the tag. 3. Select the Object(s) to which the tag can apply. Example objects include ‘Registration Statuses” and/or “Custom Registration Properties”. 4. Click Add. 5. Repeat as required for as many tags as you need. 6. Important: Add enough tags to apply to all of the following that you will use in your Signal Connector Flows (see Flow Data Source): a. Registration Statuses b. Custom Registration Properties 7. Also, add enough tags to apply to all of the following that you will use in filters for flows (see Flow Filters): a. Attendee Types b. Events

Applying Tags in an Account

In each event from which you want information to flow through Certain Signal Connector, apply tags to the relevant information: Registration Statuses and Registration Custom Properties.

(You can also tag Attendee Types and Events to filter registration records by attendee type or event: see Flow Filters.)

Default Registration Statuses

These apply to all events, so an Administrator applies the tags at the account level.

1. Go to Account Settings > Management > Registration Statuses. 2. or more Tags for each status.

Important: Even if you don’t use any standard registration statuses, the best practice is to set up tags for all of them.

It’s essential to tag at least the ‘ New ’ status (which Certain uses “behind the scenes” when first processing each registration).

Applying Tags in an Event

Custom Registration Statuses (Essential)

1. In each event, go to Plan > Event Setup > Custom Statuses. 2. Select at least one tag for each status.

Custom Registration Properties (Optional)

If any of the Flows you configure in Signal Connector (see Configuring a Flow) will activate for Custom Reg Properties:

1. In each event, go to Plan > Configure. 2. Under Custom Registration Properties, select at least one tag for each custom reg property in the event.

Standard Registration Properties (Automatic)

These tags are set up for you automatically, with names identical to the properties themselves: Complete, Badge Printed, On To Do List, Invoice Generated, and Test.

You only see them in Signal Connector. In Signal Connector, you can activate Flows for them (see Activate for). There’s nothing to edit on Certain Platform.

Attendee Types

(Optional– for use with filters – see Flow Filters.)

1. In each event, go to Plan > Event Setup > Attendee Types. 2. or more Tags for each attendee type on which you may wish to filter registrations. (see Flow Filters.)

Events

(Optional– for use with filters – see Flow Filters.)

1. In each event, you wish to include in a filter. Example: ensure that only registrations for that event are passed to Marketo: 2. Go to Plan > Event Setup > Details. 3. or more Tags for the event.

Registration Questions

(Optional– for mapping Certain fields to Marketo fields – see Mappings.)

1. In each event in which you use registration questions to capture data from attendees and wish to pass those answers and/or questions to Marketo: 2. Go to Plan > Event Setup > Questions. 3. Select just one Tag for each question. Selecting more could result in duplicate data in Marketo.

Opening Certain Signal Connector

When Signal Connector is activated for your account, the Account Settings > Implementation menu. This menu is available to Administrators. The menu includes an extra option:

Click that link to open Certain Signal Connector in a separate window; it runs separately from Certain Platform.

Note: To return from Signal Connector to Certain Platform at any time, click

Setting up a Connection

What are Connections?

A Connection in Certain Signal Connector specifies how to connect to your instance of Marketo. Marketo is the Target application.

You can have multiple connections. For example, you can have multiple connections to Marketo and another application. (Other target applications are covered in separate guides.)

Each Flow (see Setting up Flows) requires a Connection. Multiple flows may use the same Connection.

You can set up a Connection before configuring your first Flow. You also can set up a Connection while configuring a Flow. This guide assumes you’re setting up the Connection first.

Adding a Connection

As an Administrator, you may set up one or more Connections for your account. You need only do so once. Then you can use the Connections in the Flows you set up (see The Flow List, below).

1. Go to Account Settings > Implementation > Signal Connector Real-Time Data Integration. 2. As noted above, Certain Signal Connector opens in a separate window. 3. Click Connections in the left navigation panel. 4. Click Add A Connection in the Connection List page that opens. 5. Enter the details in the Connection Setup screen that opens.

Example names include ‘Marketo’ or ‘Marketo Connection’.

Use the part starting with “https://” and ending with “marketo.com”.

Example: https://app-ab13.marketo.com

For Marketo, the authentication type is currently OAuth2.

If selected, then if Marketo already has a record for the Lead whose data is being sent, that Lead will be updated where any details in Certain differ.

Example detail: their phone number.

The Signal Connector connection will take precedence.

6. Click Save & Test. 7. If the test is successful, click Close. If the test is not successful, check that the values in step 5 are all correct.

Setting Up Flows

What is a “Flow”?

A flow is a configuration to manage the flow of data from Certain to Marketo.

You create Flows from the landing page in Signal Connector. (See Configuring a Flow below.)

You may configure several flows for an account. Those flows might all use the same Connection.

You only need to configure a flow once at the account level. When a flow is complete, it will start picking up data for each event in that account within about a minute.

The minute’s delay is because Signal Connector runs independently from Certain Platform. If you edit a flow, the same slight delay occurs before that change takes effect in the processing of the registrations.

The Flow List

As an Administrator in Certain Platform, go to Account Settings > Implementation > Signal Connector Real-Time Data Integration.

As noted above, Certain Signal Connector opens in a separate browser window.

The main screen in Signal is the Flow List, which lists all flows.

The Status column shows whether a flow is completely set up.

The Active column shows whether the flow is running. Click the toggle button to change a flow from Active to Inactive. Click the toggle button to change a flow from Inactive to Active.

Configuring a Flow

Click ADD A FLOW to start setting up a new flow.

See screenshot overleaf.

The configuration consists of:

‘Live’ or ‘Test’

The Live toggle switch determines whether your Flow is Live or Test.

A Live Flow will pick up all live registrations in live events. A Live Flow will ignore test registrations, even in live events.

A Test Flow picks up all test registrations. A Test Flow includes all registrations in test events. A Test Flow also includes any registrations marked as ‘Test’ in live events."

Best Practice: Set a new flow up as Test—and test it—before setting it to Live.

Flow Data Source

Next, specify the Source of data for the flow (optionally applying Flow Filters).

The Source of a Flow is what the Flow will watch for in your data in Certain. The Flow activates based on that data.

For example, the flow might watch for any change to a Registration Status. The flow activates if an attendee’s status has changed to a status tagged as ‘Registered’.

Available sources

You set a flow to watch for any one of the following:

Note: You can always save an incomplete Flow and complete it at a later date.

As soon as a Flow is complete, it will start picking up data after the usual minute’s delay.

Activate for …

Choose what the flow should activate for by selecting one or more tags in each appropriate object’s dropdown list.

As shown in the screenshot above, you can activate for tags applied to Registration Statuses and/or Registration Properties. (The latter includes both Standard Reg Properties and Custom Reg Properties.)

Other options may be added depending on what the Flow is watching for:

The tags available for selection are those set up for that object. (See Setting up Tags.)

For example, the tags for Registration Statuses include Registration Status tags.

You can apply those Registration Status tags to:

Flow Filters

You can filter the data going into a flow by selecting fields in any of these three filter types:

The flow will only include a registration if it meets the rule(s) specified in the filter.

Available fields:

— standard event fields (e.g., Event Code)

— custom event fields

— event tags

Available fields:

— standard profile fields (e.g., Position)

— custom profile fields

Available fields:

— tags that can be applied to Attendee Types

Note: For custom fields you can only select “enumerated” questions.

Those enumerated questions have pre-configured answers.

Examples of question types include Select, Multi-select, Checkbox, or Radio.

Flow Destination

Select Marketo from the integrations set up by Certain for your account.

Setting up a Destination

1. Give the Destination a name of your choice.

2. Select the Connection to use.

Note: You can instead click New Connection to add a connection.

The process to set one up is the same as described on Setting up a Connection.

3. Select the action for this connection from those listed as available:

Your choice of action determines the other configuration options.

Mappings

The Available Mappings option is available for most actions. Those actions include ‘Trigger Campaign’, ‘Create/Update Lead’, and ‘Form Post’.

A mapping specifies how each target field in Marketo matches a source field in Certain.

Select a mapping from the drop-down list.

If nobody has set any mappings up yet, or you need something other than one of the existing mappings, click New Mapping to add one:

1. Give the mapping a name of your choice.

Best Practice: For multiple mappings used for different flows, make the names self-explanatory.

Examples include ‘Lead Mapping’ and ‘Form Mapping’

2. The left column lists Marketo fields as the “target” fields.

Under each target field is the default “source” field in Certain matching that target field.

Example: target field ‘Salutation’ defaults to source field ‘Prefix/Title’.

This default means the value of the Salutation field in Certain will populate the Prefix/Title field in Marketo.

3. By default, only the First Name, Last Name and Email fields are mandatory.

Select the checkbox next to a target field to make it mandatory.

This is not normally fixable.

This situation would not go into the Retry Queue.

4. Click the x after a source field label to delete that field.

Click to add a new one.

Note: You can concatenate multiple source fields for the same target field.

You can also type fixed text.

Example: for target field ‘Title’, you could choose source fields ‘Position’ and ‘Organization’. Use two spaces and “@” to separate the two source fields.

The Certain fields you can choose from as the source of the data going into the target fields in Marketo include:

One field also exists for the answer.

(See page 5 about not using the same tag for more than one question.)

5. In the second column, select a transformation option for each field.

The default of no selection sends the data to Marketo unchanged.

The options are:

Note: You can select more than one transformation for a field.

Example: change a field to Proper Case and trim it.

6. At the end of the list you can Add Target Fields and select source fields for them.

To delete a field from the mapping, click DELETE at the end of that row.

If you’ve selected a mapping then two other buttons are enabled:

A third button is also enabled:

Use Refresh Target Fields if you don’t find a target field you were expecting in an existing mapping.

Technical note: This is likely for new fields added since a connection was created.

The reason is that target fields are cached when a connection is tested.

A refresh updates the cached mappings.

Campaign ID

The Campaign ID is required if your action is ‘Trigger Campaign’ or ‘Create/Update Lead’.

There are two options:

If you have a unique campaign for each event, use a custom event question to specify the campaign ID.

(See Registration Questions.)

Select that question here.

To move all attendees to a single campaign, regardless of event, enter the campaign ID here.

Note: If you specify both an event question and an account-level campaign ID, then the event question-based campaign will take precedence.

Form

If the selected action is Form Post, complete the following:

You then select the target fields and map them to the source (Certain) fields, as described under Mappings above.

Metrics Dashboard

To see the statistics available in Signal Connector, click Metrics in the left navigation panel when looking at flows.

The choices in the new navigation panel for Metrics depend on the flows and their targets.

The first choice will be Insights, as illustrated and described below.

Other links will be, for example, to Leads Created and Form Posts. Those links each work in the same way as Account Insights.

Account Insights

Select whether you want to see Live Flows or Test Flows.

Select the period for which you want to see the data.

Examples include:

There are three tabs: Summary, Troubleshooting, and Activity Feed.

Summary tab

This is the default tab on the Insights page.

The figures shown depend on the flows and actions.

For some figures, you can click the number to drill down further. For example, click Unique Registrations to see the registrations processed by any flows in your selected time frame.

You can filter or search for records when you’ve drilled down. Example: filter on an Event Code to see only the registrations in that event.

Remember these figures are for the whole account. The figures include all events and registrations.

For each of these you can click the number to drill down to details.

This value increments each time a registration is created or updated in Certain and then processed by a flow in Signal Connector.

Note: This value will often include the same registration more than once.

Example: creating a registration and then updating it twice would total three “changes”.

This value may be the most relevant figure on the page.

Example: if you only have one flow with one action, this could be the same as Changes Processed.

Multiple flows and multiple actions per flow can increase this number.

Example cause: a registration having an untagged status.

This value is not related to whether the flow is shown as ”Active” or ‘Inactive” on the Flow List.

This would apply only if a Target were Eloqua.

This value is the number of form posts.

Drilling down into the failures provides a high-level view for troubleshooting.

For example, you can see why an action has failed.

After you address the cause, you can expedite the fix in Signal Connector by going back to Flows and clicking Retry in the left navigation panel.

See Retry Queue.

Troubleshooting tab

The second tab on the Insights page shows information you may find useful for troubleshooting.

Example: if some registrations are not processed because a Registration Status isn’t tagged, this gives you the chance to rectify that. Then registrations can be processed on the next retry.

The numbers shown are as follows. Click a number to drill down to see details of the actual records.

Maximum automatic retries per action = 3.

Example: if an action was retried twice, this number increases by 2.

Example: a lead could not be created because a mandatory target field had no value in the source field.

See ‘ Mappings ’

Categories include “General”, “System”, “Config”, “Connection”, etc.

Activity Feed tab

The third tab on the Insights page lists the registrations processed. The page notes success or failure. The page also includes Registration Code, Event, Flow, etc.

This is a rolling history, by date. This page is another way to access lower-level data you could see by drilling down in the Summary or Troubleshooting tabs.

The Retry Queue

When an action fails it usually joins the “ Retry Queue ”. It takes its turn to run again. Failures that can’t be resolved, such as missing mandatory fields, are exceptions. Those exceptions don’t join the queue.

An action can be retried up to three times. After three retries, the action does not rejoin the queue.

To see the Retry Queue, click Retry in the left navigation panel on the Flows page.

Causes of failure include ones under your control as a planner. Example: a registration with a status that hasn’t been tagged. Causes also include technical ones. Example: a connection being down.

Where you can resolve the cause of a failure, such as tagging a registration or setting a flow back to being active, that’s all you need do. The action should succeed when retried.

For other failures that don’t resolve themselves, you probably need to contact your administrator or ask Certain for help.

The interval between retries depends on the severity of the reason. The more serious the reason, the sooner the retry.

Filtering the Queue

You can filter the records shown in the Retry Queue using these three filters:

Submitting to the Queue

When you click an item in the Retry Queue, you see its full details.

If that knowledge is enough for you to solve the problem, then once you have done so you can click Submit to Retry Queue. Submitting to Retry Queue adds the item straight to the front of the queue.

Replaying a Flow

If you change an aspect of a flow while it has been running for some time, such as changing its filters, you may want to replay that flow for the same registrations. Replay should happen as if the changes had been made earlier.

This is not something you can do directly. You can ask Certain to arrange it for you. You may be able to specify a date range. You may also be able to specify an event.

Source: https://platform-support.certain.com/hc/en-us/articles/10901541136151-Signal-Integration-with-Marketo-Guide

Published:

Keywords: Certain Signal Connector, Marketo, Signal Connector, OAuth2, Flow, Retry Queue