Quick answer: A personalized email and a QR code are separate parts of a promotion. Your email tool delivers the right offer to the right contact; your redemption system decides whether that offer is valid, what it grants and whether it has already been used. Start with the redemption capability supported by your installed system, then build the email around it. A different-looking QR image for every recipient is not, by itself, a single-use promotion.
Define the offer before generating codes
Write the promotion in plain language: the qualifying purchase, the exact benefit, eligible games or attractions, valid dates and hours, participating location, redemption limit and exclusions. Decide whether it is intended for a person, household, game card or transaction. Those are different limits, and the system needs a way to recognize the chosen unit.
For example, “buy a qualifying $20 play package and receive $5 in promotional play on Tuesdays through November 24” still needs rules. Is promotional play usable on prize games? Can it combine with another offer? Does the paid package qualify when bought using a gift card? Can a forwarded email be redeemed? Have the answers ready before guests arrive.
Keep an internal promotion record with an owner, start and end times in the venue's time zone, approved value, intended audience, redemption method and stop condition. Assign a campaign ID that stays consistent in the email, redemption report and staff instructions.
Choose a shared code or individual tokens deliberately
| Approach | Useful for | Control it does not provide alone |
|---|---|---|
| One shared offer code | A broad public offer where sharing is acceptable. | It cannot reliably establish one redemption per person merely because the code was emailed. |
| One unique token per recipient | Tracking which issued offer was used and enforcing a usage limit on that token. | It does not prevent the recipient from forwarding an unused token. |
| A token linked to an account or game card | An offer that needs to apply to a recognized customer's record. | It still needs a supported identity check, clear guest instructions and a recovery process. |
A QR image can encode a shared offer, a unique identifier or a website address. Decide which payload your redemption system expects. Do not put a guest's name, email address or other unnecessary personal details directly into a scannable code.
What the published Intercard and Constant Contact documentation establishes
Intercard's help page says an iCashier POS can scan promotion and e-commerce QR codes when equipped with a 2D scanner, separately from the redemption-terminal scanner. Its e-commerce page describes purchased products producing a QR code that a guest can show or print for redemption at an iTeller. These establish specific scanning and purchase-redemption workflows; they do not establish a turnkey Constant Contact integration for individualized promotional codes. [1] [2]
Constant Contact documents inserting contact details and custom fields into email text. Its instructions also explain fallback text and note that previews or test sends can show fallback values rather than an individual contact's custom field. That makes testing actual recipient data essential. Those text-personalization features do not, by themselves, generate a unique redeemable QR image or mark a code used in Intercard. [3]
Ask Intercard which promotion type your software version supports, whether it can generate a batch of unique identifiers, where redemption is recorded, and how per-code, per-card or per-customer limits work. Ask Constant Contact how your selected editor can insert the supported token or redemption link. Obtain an actual demonstration before assuming the two systems connect automatically.
Build the smallest dependable workflow
- Create and approve the offer. Save its rules in the redemption system and confirm the correct location, period and benefit.
- Issue the identifiers. Use the redemption platform's supported process. Preserve the mapping between issued token, campaign and intended recipient where needed.
- Prepare the mailing data. Import only permitted contacts and required promotion fields. Treat codes as text so an import does not remove leading zeros or alter long values.
- Compose the email. State the benefit and restrictions clearly, with a useful subject line and a plain-text fallback code where supported.
- Validate at the venue. Staff or supported kiosks check eligibility, issue the benefit and record the completed redemption.
- Reconcile after sending. Compare issued offers, successful redemptions, rejected attempts, manual overrides and actual campaign cost.
If native bulk generation is unavailable, begin with a small vendor-approved manual pilot. A spreadsheet may help track issuance, but it is not a reliable real-time redemption authority across several busy terminals. Avoid building an unsupported automation that writes directly into production tables.
Specify the controls that protect the offer
Ask the provider to show how two terminals handle the same token at nearly the same time. For a single-use offer, a second terminal must not grant the benefit simply because both checked the token before either recorded completion. The provider should explain how its supported process prevents that race.
Require recognizable results for valid, expired, already redeemed, wrong-location and unknown codes. Keep authorization separate from presentation: a cashier seeing a genuine-looking screenshot is not the same as the system validating a token.
Decide how failures are handled. If the system marks a token used but the game card never receives the benefit, staff need a traceable recovery procedure. If the benefit is issued but the screen times out, retrying should not silently issue it again. If a personalized link is used, merely opening the email or viewing the offer page should not consume the benefit.
Restrict manual overrides, record a reason and retain the original redemption record. Give the campaign owner a supported way to stop future redemptions if a configuration error appears. For any custom integration, have its developer document token generation, access control, duplicate prevention and logs before a public launch.
Test what guests and staff will actually see
Create a small internal audience with deliberately different test records: a valid token, an expired token, an already-used token and a record missing its promotion field. Send a controlled campaign to that audience through the same workflow planned for customers. A generic test-email button alone may not prove contact-specific merging, given Constant Contact's documented preview behavior. [3]
- Open the message on common phone email apps, with images enabled and disabled.
- Scan from a dim phone screen and from a printed copy using the actual venue scanner.
- Try the fallback entry method and verify that it reaches the same redemption record.
- Forward an unused test offer and confirm the result matches your stated transfer policy.
- Redeem once, scan again and check both the guest message and the audit record.
- Confirm the exact promotional value, eligible use and any qualifying-purchase condition.
Keep a short staff script for each rejection. “This code shows a previous redemption; a manager can check that transaction” is more useful than an unexplained “invalid” message.
Use the right audience and clear email terms
Constant Contact requires permission to email contacts and prohibits purchased, rented and scraped lists. Keep the source of each contact and their subscription preference; do not assume possession of a booking email address establishes permission for every future campaign. Use a clear opt-in process for new marketing subscribers. [4]
For U.S. commercial email, the FTC's CAN-SPAM guide covers accurate sender information and subject lines, advertisement identification, a valid postal address, a clear opt-out method and honoring opt-outs within ten business days. Other jurisdictions may impose additional consent rules. A promotion remains a marketing message even when it includes a personalized code. [5]
Measure redemptions and contribution
Track delivered messages, offer redemptions, qualifying purchases, promotional value granted and support incidents. Keep scans separate from completed redemptions. A person might scan repeatedly or view the offer without visiting.
Illustrative example: If 500 offers are delivered and 40 are redeemed, the redemption rate is 8%. If the 40 qualifying purchases total $1,000, that is associated purchase revenue, not proof of $1,000 in incremental revenue. Some customers may have visited anyway. Estimate contribution after the offer's real variable cost and compare with an appropriate non-promoted period or a carefully designed holdout group.
Run the first campaign small enough to review every exception. Expand only after the recipient data merges correctly, the venue enforces the stated rules and the reports explain what happened. Reliable redemption is the foundation of a promotion guests will trust.