01Native connector: Shopify
Shopify is the only native connector. It works without Zapier, Make or code on your side.
Works with Shopify
- Capability
- Issues each reward as a real Shopify discount code, created in your store ahead of time. A paid order that uses the code marks the reward redeemed and counts towards missions and points.
- Data direction
- Both ways: discount codes go to Shopify, paid orders come back to Portico.
- Set-up
- One connection per store, through a custom app that Luminbrane sets up with you. Credentials are stored encrypted and never shown again.
- Limits
- Shopify stores only. A reward counts as redeemed when a paid order uses its code. Other e-commerce platforms connect through the webhook-compatible routes below.
Webhook-compatible
Signed interfaces you connect to your own endpoint, to Zapier or Make, or to any CRM that accepts webhooks. There is no built-in CRM connector.
Outbound webhooks
- Capability
- Sends lead.captured, reward.awarded, reward.redeemed, quiz.completed, calculator.completed and prediction.settled as signed JSON as they happen.
- Data direction
- Out, from Portico to your endpoint, Zapier or Make.
- Set-up
- Add an endpoint and choose its events in the console.
- Limits
- Each event carries a stable id so your receiver can ignore retries. A delivery log shows every attempt, and a failed delivery can be sent again with the same id. Your receiver checks the signature.
Business events API and CSV
- Capability
- Records what happens after the campaign, such as lead.qualified or purchase.completed, matched to the campaign that brought the person. Verified events count towards missions and points.
- Data direction
- In, from your systems to Portico.
- Set-up
- A signed API call from your server, or a CSV upload in the console.
- Limits
- An event sent twice is stored once. Events reported only by a browser never count towards missions or points.
Redemption callback and CSV
- Capability
- Tells Portico a code was used at your till or checkout, so the reward moves from claimed to redeemed.
- Data direction
- In, from your till or e-commerce platform to Portico.
- Set-up
- A signed callback, or a CSV of redeemed codes with a preview of what each row will do.
- Limits
- A code reported twice is redeemed once. An email sent is never counted as a redemption.
Postbacks and pixel
- Capability
- Registration and first-deposit attribution for iGaming campaigns.
- Data direction
- In, from your tracking platform or confirmation page to Portico.
- Set-up
- A server-to-server postback URL, or a pixel on the confirmation page.
- Limits
- Kept for campaigns already using them; new set-ups use business events. A pixel reports from the browser, so it never counts towards missions or points.
On your own site: embeds, consent and pop-ups
Every campaign has a hosted play page, and the embed loader places it on approved sites. The embedded game asks your consent tool before it runs analytics, so your cookie banner decides. The same loader can open the game as a pop-up after a delay, at a scroll depth, on exit intent (desktop only), on a click or from your own script, limited to the pages you choose and to once per session, once every few days or never again after it is closed.
Known customers and returning participants
Signed identity lets your site associate an embedded visit with an existing customer account. Your backend signs the identity; the game never needs a password or access to the account. Without it, a participant can verify their email with a 6-digit code and is recognised within that brand only.
Reward fulfilment stays with your business
Portico does not connect to a payment system or a wallet. It allocates codes, gift cards and offer links, creates Shopify discount codes, keeps its own points ledger or records a manual reward. Your checkout, till or platform honours the reward and decides who is eligible.
Shopify is a trademark of Shopify Inc.
