To begin you may need to update you API User Role permissions to allow dynamic content to fully function. The required permissions for dynamic content to work are:
Read-Only Lead (sometimes listed as Read-Only Person)
Read-Only Custom-Object
Step by Step Instructions for Marketo Dynamic Content Configuration
Navigate to the Admin Platform > Integrations page
For the new integrations page, locate the Marketo tile and click on Dynamic Content Settings for the instance you want to setup
3. Create a Knak variable configuration token. This token will store all the data fields or Marketo segments that your company will use in Knak for dynamic content.
This can be created in any folder, however we recommend placing it in your default workspace in one of your top level folders so its accessible to all folders on the same level or below.
4. Upon selecting a folder, the button “Create New Config” will appear. Click it and scroll to the bottom of the modal. This will automatically create a new token in your Marketo instance called {{my.Knak Variables}}
5. Click on “Add” to open the token’s location in a new tab. This will open a new Marketo tab to the folder you have chosen above
6. Locate the “{{my.Knak Variables}}” token and edit it.
7. Drag all of the variables you want to be able to use in Knak into the script area, so that the variable is checked off in the right panel, and exists in the script as well. Be sure to click save.
You can add variables or existing segments here, for segments, they will begin with 'Segmentation_xxx' You can select & drag in a segment the same as you would a variable:
8. Navigate back to the Dynamic Content Settings in Knak. Click on “Sync” to sync in the variables that have been set up in Marketo into Knak
9. The variables that were set up should appear, hovering over them should display their variable syntax and type. Any segmentation variables that were brought in will be blue.
If you want to edit the dynamic content tokens later, click on the dynamic content icon on the upper right corner of the Marketo tile
Note:
If you are using tokens in a dynamic content segment, you must set use the ${<Name of the velocity script token>} syntax in the Merge tags under the Admin settings.
To change the location of the Knak variables in Marketo (the Folder you chose in step 3), you need to select a new folder and click Create New Config again. This integration will be connected to the new folder, but you will need to re-add the variables in Marketo as in step 6 and 7
For example, this is how you'd set up the lead city merge tag if you wanting to use the tag in a dynamic content segment
Check out our other articles on Dynamic Content.
Step by Step video on how to configure dynamic content in Knak:
Walkthrough video of Dynamic Content from Knak to Marketo:
Points of Consideration
Sync Location and Email Sending
When syncing an email into Marketo, script tokens are automatically generated which contain the email’s dynamic content. The tokens are synced to the nearest ancestor program. When sending emails using a Smart Campaign in Marketo, the Smart Campaign must be in the same program as the email. If not, the dynamic content will not render on email send.
Emails synced into an Email Program should always send correctly when sending through the Email Program.
Sharing Segmentations
When syncing to a different workspace from where the configuration was created, that workspace may not have access to the segmentations you may be using. If you want to sync to a specific workspace using a specific Marketo segmentation, ensure the segmentation is shared with that workspace.
Marketo’s 100KB token length limit
Marketo limits the combined length of velocity tokens in an email to 100KB. If an email synced to Marketo is going to surpass this limit, we will show a warning during the sync. Marketo will also render the error on preview. To reduce the length of velocity tokens there are a few things you can try.
Split up long text into dynamic and non-dynamic parts, limiting the amount of text in dynamic blocks
Remove the tokens from the plaintext version of the email
Reduce the amount of dynamic content used
FAQs
I followed the steps for set up but my company token doesn't seem to be working, is this a bug?
For configuration variables sync we only support Lead variables in Marketo (Lead.xxx). We do not support Company variables (i.e., {Company.Company Name}). If you are trying to add a token such as ${Company.Company Name}, we recommend replacing this with a different token with a similar effect for lead variables such as ${Lead.Company}
When should I use local segments versus global segments?
Global segments are for re-use across multiple emails and can be used in modules. local segments are just for an individual email.
When should I use the default hide variant feature?
This is for when you don’t want to display any content in that block if none of the conditions match. A use case would be showing a special offer to certain groups. You would make the special offer element dynamic and target only the groups that you want to see it via the segment builder. If you make it hidden by default anyone who is not part of the group/groups that are targeted would not see the offer.
If you have any questions, reach out to support at support@knak.com or the chat bubble in the lower right corner.