Validation workflow

1. Create or update a conversion type.
2. Trigger the conversion from a test session.
3. Use conversion testing tools in settings.
4. Confirm conversion appears in reporting views.
5. Validate value and attribution for expected channel/journey.

QA checklist

• Trigger is firing exactly once per intended action.
• Conversion value matches expected static/dynamic value.
• Conversion appears in the correct site and environment.
• Journey attribution aligns with known traffic source.

Recommended rollout pattern

• Validate in staging first.
• Launch one conversion type at a time.
• Monitor first 24-48 hours after deployment.

Troubleshooting

• Test passes but reports lag: wait for processing window and re-check.
• Duplicate conversions: remove overlapping triggers.
• Attribution mismatch: inspect session path and consent status.