Server events to Meta are off. This tool sends nothing to any pixel unless a code is set to, one code at a time, in the form above. Default is off.
Export. Every scan, with code, placement, time, country, device and referrer.
This page has no password, so the export leaves out scanners' IP addresses, which are their personal data rather than yours. Codes can also only point at brand destinations, which is what stops the short links being turned into something they should not be.
Worth being straight about what the CSV can do. It is for counting and analysis, which placement pulled, which day, which city. It cannot be uploaded to Meta as a custom audience. A customer list audience matches on email, phone or name, and a QR scan gives none of those, only an IP and a device string, which Meta does not accept for list matching. No tool can get around that.
If you do want to retarget scanners, it already happens without this tool touching anything. They land on the site with utm_source=qr attached, and the pixel that is already on the site records the visit like any other. Build it in Ads Manager, Audiences, Create audience, Website:
Use utm_content contains a placement value for one code only. This does not apply to a code pointing at Instagram, since that is not your site and your pixel never runs there.
Two ad accounts. A pixel audience belongs to the business, not to one ad account, so a single audience can be used from Feels Good Club and Feels Good Club V2 both, with no rebuilding. V2 currently has no pixel attached to it, which has to be fixed before it can use one.