Thanks for helping improve these blueprints.
Open an issue with: the scenario, what you expected, what happened, and (if relevant) the Make.com error text. Never paste real Pixel IDs, access tokens, or customer data.
- Keep credentials as placeholders (
YOUR_PIXEL_ID,YOUR_ACCESS_TOKEN). - Test the scenario end-to-end in Make.com before submitting.
- Update the relevant
field-mapping.mdif you change module mappings.
Found something sensitive (a committed token, a data-leak path)? Email the maintainer via stackarchitect.xyz rather than opening a public issue.