Event Customiser FAQ and troubleshooting

Common questions and solutions for the Event Customiser.

Use this page to answer common questions and troubleshoot Event Customiser issues.

General

• Does the Event Customiser affect all destinations? No. Each customisation applies to one event and one destination only.

• Do changes affect historical data? No. Only future events use the new configuration.

• What happens if a field path has a typo? Littledata skips that mapping for that event. The event still sends.

• Can I customise client-side events? Support is limited and depends on the destination.

• Can I create multiple customisations for one event? Yes. They run in this order: Filter, Modify, then Clone.

• Is there a limit on custom parameters? Yes. Limits vary by destination. The button disables at the limit.

Field mappings

• What is a locked mapping? It uses a fixed source and destination. You cannot edit or remove it.

• Can I remove a standard mapping? Usually no. You can override the source, but not remove the mapping.

• Why is my source field empty in the preview? The path may be wrong. The sample event may be old. The field may be conditional.

• How do I use a static value? Choose Static value in the source dropdown, then enter the value.

Custom Data Sources

• My metafields do not appear in the source dropdown. Select them in Settings → Custom Data Sources. Then refresh and reload.

• How long does metafield discovery take? Most shops finish in 1 to 5 minutes. Large shops may take longer.

• Do metafields slow down webhooks? No. Shopify handles metafield inclusion efficiently.

Filters

• My filter does not seem to work. Check the field path, the operation, and that the filter is saved.

• Can I filter events for all destinations at once? No. Filters are per destination.

Clones

• How do I differentiate a cloned event? Set the event name to a static value and map it to events[0].name.

• Can I remove all standard parameters from a clone? No. Locked mappings always remain.

Trigger conditions

• Do conditions support OR logic? Not in one customisation. Create separate customisations instead.

• What field paths can I use in conditions? Any field in the source dropdown, including configured metafields.

• Can I use regex in conditions? Yes. Use the matches regex operation.