Skip to main content
All CollectionsMoEngage
MoEngage - Known Issues
MoEngage - Known Issues

Review our known issues before continuing with MoEngage

Updated over a week ago

Please be aware of the following issues you may encounter whilst using Jacquard with MoEngage:

  • If your human control variant contains personalisation variables, then it will require a different fallback method to the | default filter. Instead use an if statement:

    {% if {{variants.variant_text}} == blank or {{variants.variant_text}} == null %}
    PASTE YOUR HUMAN CONTROL HERE
    {% else %}
    {{variants.variant_text}}
    {% endif %}
  • ContentAPI code snippets can't be stored in Content Blocks so you will need to store the code snippets for the subject line and open pixels outside of the platform (or bookmark the support page).

  • Maximum Throttling limit is 60000 requests per minute.

  • Jacquard Dynamic Optimisation Start Schedule must be at least 30 mins before the MoEngage deployment begins.

  • When testing your email message in MoEngage, you must send to a custom segment (not an individual email address) in order for the API calls to be made.

  • Avoid using double quotation marks in the default fallback language.

  • Talk to your MoEngage customer success representative to ensure the open tracking pixels returned via the ContentAPI are not HTML encoded.

Did this answer your question?