Knak requires access to Marketo variables and custom objects to support Dynamic Content.

Verify that the Marketo API user has the following permissions:

Without these permissions, Knak cannot access the variables required for Dynamic Content.

If you recently updated permissions, sync your variables again from the Dynamic Content Settings page.

Dynamic Content only supports Lead tokens.

Replace:

With:

If only the default Dynamic Content variant appears after syncing:

Related article: How to Set Up Marketo Dynamic Content

If your Dynamic Content previously worked but now only displays the default content, the Marketo segmentation associated with your Knak Global Segment may have been renamed.

After syncing, Knak continues to reference the original segmentation name. If that name changes, the mapping breaks and Dynamic Content no longer renders correctly.

Marketo tokens have a maximum size limit of 100 KB.

Large amounts of Dynamic Content can cause the generated Velocity script to exceed this limit.

Yes.

To use Marketo tokens inside Dynamic Content segments, first configure the variables in the {{my.Knak Variables}} token.

Then configure the corresponding merge tags in Knak.

Use the following syntax:

If you are unsure which variable to use, review the variables configured in your Marketo token.

Related article: How to Set Up Marketo Dynamic Content

No. Dynamic Content created in Knak cannot be edited directly in Marketo.

When you sync Dynamic Content from Knak to Marketo, Knak converts the Dynamic Content logic into Marketo Velocity script tokens. The Dynamic Content variants are stored within the token rather than the email itself.

As a result:

To update Dynamic Content created in Knak:

Any changes made directly in Marketo may be overwritten during future syncs.

The setup depends on how your Custom Object data is stored.

A standard object field stores one value for each person. For example, First Name has only one value for each lead.

A Custom Object can store multiple records for the same person. For example, one lead might have multiple event attendance records. Each record contains the same field names, such as Event Location, with different values like Chicago, Ottawa, or London.

If each lead has multiple Custom Object records, selecting the correct value requires searching through those records.

Dragging a Custom Object field into a token does not search all available records. It only returns a single record. In most cases, this is the most recent record. This behavior is not guaranteed.

Knak does not currently support searching through multiple Custom Object records with a no-code solution.

A lead has attended three events. Each event creates a separate Custom Object record. If you insert the Event Location field into a token, Knak returns only one of those records. It cannot automatically find the record that matches a specific event.

This is expected behavior. Cloning emails with Knak Dynamic Content to another Marketo program is not supported.

Why this happens:

What to do instead:

Sync the email from Knak directly to the new Marketo program. This creates the required Dynamic Content tokens in the destination program.

No. The integration only supports syncing assets from Knak to Marketo.

If you need to update a synced asset, make your changes in Knak and sync the asset again. While some edits can be made directly in Marketo, maintaining the source asset in Knak helps prevent changes from being lost during future syncs.

The Marketo search field only displays up to 150 recently updated programs. Programs that have not been updated recently may not appear in the search results, even if they were created recently.

This limitation exists because Marketo does not support searching across all programs by name through its API. As a result, Knak can only search a recent set of updated programs.

If you don't see the program you're looking for, select Browse Programs. This allows you to navigate your Marketo folder structure directly and find programs that may not appear in the search results.

Tip: Search is intended to help you quickly find recently updated programs. Use Browse Programs to locate older or less recently updated programs.

Knak includes two versions of each button to ensure optimal rendering across email clients.

Buttons cannot be edited directly in the standard Marketo editor.

To update a button:

While some button values can be updated through Global Variables in Marketo, it is recommended that you make changes in Knak and sync the email again. This helps keep your source content up to date and prevents changes from being overwritten during future syncs.

This behavior is expected.

Buttons may appear tokenized in HTML downloads to support Outlook rendering and Marketo editing functionality.

Upload the HTML to Marketo using the standard Knak workflow. The buttons render correctly when the email is sent.

If your email displays duplicate headers or footers after syncing to Marketo, Marketo may be automatically adding a global header or footer.

Global headers and footers are controlled in Marketo under Admin > Email.

Check these settings if your Knak email already includes a header or footer. Disable the applicable Marketo setting to prevent duplicate content.

Marketo does not allow updates to emails that have an active Champion/Challenger (A/B) test.

This is a Marketo Application Programming Interface (API) limitation.

To update the email:

If a folder appears in Knak but no assets are returned when you select it, the Marketo API may be unable to retrieve the folder's contents.

Common causes include:

Confirm the folder is active and accessible in Marketo. Verify that the API user has the required permissions.

If the folder name contains special characters, recreate the folder using a simplified name. When possible, use dashes (-) instead of slashes (/) in folder names.

If the issue continues, recreate the folder. Move the assets into the new folder.

Marketo may consider the asset corrupted when a dollar sign is placed directly before a token.

For example:

${{lead.Custom Price}}

Use the following workaround:

$#**{{lead.Custom Price}}

After updating the token, sync the asset as a new email.

This error means your Marketo instance may have reached its daily Application Programming Interface (API) request quota.

Check your API usage in the Marketo Admin panel. If you need more help, take a screenshot of the API usage and share it with your Marketo administrator or Marketo support team.

You may see the following error when syncing an asset:

Operation timed out after 300000 milliseconds with 0 bytes received

This is a known Marketo issue. Marketo has provided fixes for this issue in the past.

Contact Marketo Support and reference case numbers 02542654 and 02675889. Both cases were resolved through a Marketo update.

In the meantime, try these workarounds:

If Marketo Support needs more information about the request from Knak, contact Knak Support.

You may see this message even when your email does not contain an emoji.

This can produce a Marketo 611 error. Error 611 can occur when Marketo encounters an unknown issue while processing the request.

Try syncing the email as a new asset. You can also manually upload the email to Marketo.

If syncing as a new email works, contact Marketo Support. Share the request ID so Marketo can investigate the failed request.

Check whether Knak displayed a warning during an earlier sync.

You may also see API errors in the Marketo console when Knak retries part of a sync. An API error in Marketo does not always mean the full sync failed.

Knak displays an error when the sync cannot be completed.

This error occurs when Marketo receives too many API requests within a short period.

Check whether other tools or processes were using the Marketo API when the error occurred.

To review your API traffic:

This error may be caused by an invalid Velocity script in Marketo. The script may not appear directly in your Knak email HTML. It can be added through a Marketo {{my.Token}}.

To troubleshoot the error, remove the tokens from the email content in Marketo. Preview the email again.

If the error is gone, review the scripts used by your Marketo tokens.

If your sync error is not listed above, use the Marketo REST API Error Codes documentation as a first troubleshooting step.

Search for the error code returned by Marketo. The documentation explains common Marketo error codes and what they mean.

If you still need help after reviewing the error, contact Marketo Support or Knak Support for further troubleshooting.

If your subject line contains emojis or special characters, Marketo may display encoded text such as:

This is expected behavior within Marketo.

The encoded text only appears in the editor preview in Marketo.

Recipients see the correct characters when the email is sent.

Some Outlook test emails may display encoded text when the subject line contains special Unicode punctuation.

For example:

The ellipsis character may cause encoding issues.

Replace the ellipsis character with three standard periods:

If no preview text is configured, inbox providers may display the first readable content from your email.

This can include:

To control what appears in the inbox preview area, add Preview Text to your email in Knak.

If you do not want any preview text to appear, add a zero-width character to the Preview Text field.

Example:

This prevents inbox providers from displaying content from the email body.

If the Preview Text box is not selected after you sync your email to Marketo, this is expected behavior. Your preview text will still display as intended when you send your email.

The Marketo Application Programming Interface (API) does not allow Knak to sync your preview text directly into Marketo's Preview Text field. Instead, Knak adds your preview text directly to your email's code when you sync your email to Marketo.

This means:

Knak's preview text gives you more control over what appears after your subject line.

Knak helps prevent unwanted text from your email content from appearing after your chosen preview text. This creates a cleaner inbox preview.

For more details, see Preview Text Done Right.

If preview text appears twice, verify that Include Preheader Text is disabled in Marketo.

Marketo may append its own preheader content, resulting in duplicate preview text.

Marketo has a 100-character limit for landing page template names.

When you sync a landing page, Knak adds 14 characters to the template name to create a unique ID. This means your landing page name in Knak should be 86 characters or fewer to stay within Marketo's 100-character limit.

If you receive this error even though your landing page name is under 100 characters, shorten the name to 86 characters or fewer. Sync the landing page again.

Marketo supports only one embedded form per landing page. Adding multiple Marketo forms to the same page can cause unexpected behavior or prevent forms from working correctly.

Common issues include:

If your Marketo form uses a two-column layout, the setup depends on the type of field.

Checkbox fields require custom Cascading Style Sheets (CSS) to display and align correctly in two columns.

Add custom CSS in Marketo to control the checkbox layout and alignment.

If other fields are not aligning correctly, review the two-column layout in Marketo.

Check the following:

Marketo Munchkin tracking code can interfere with the Open Graph tags on your landing page. This may affect how your landing page appears when you share it on social media.

To avoid this issue, add your Munchkin tracking code using one of these options:

For more information about Open Graph tags, see Open Graph Meta Tags.

Need more help? Contact support via live chat within Knak using the chat bubble in the bottom right corner or email support@knak.com.