Loyalty integration

Pepper + CaptiFi

Create opted-in WiFi guests as customers in your Pepper account, so walk-ins feed the same CRM as your order-to-table and loyalty customers. Free trial.

Start Free Trial See all integrations

Overview

What does the Pepper integration do?

The Pepper integration is a native connector, shipped in August 2026. Add the Application ID and API Token issued by the Pepper team to the CaptiFi Integrations page and every WiFi guest who accepts marketing is created as a customer in your Pepper account within minutes, with name, email and consent recorded, ready for your Pepper campaigns, offers and loyalty. For hospitality venues running Pepper's branded ordering app. Growth plan and above.

The Pepper integration is a native CaptiFi connector, shipped in August 2026. Pepper (pepperhq.com) powers branded ordering for hospitality: order to table, click and collect, pay at table and loyalty, all through a venue's own branded app. Its customer base holds the guests who order and earn rewards, but guests who only join the WiFi normally leave nothing behind. CaptiFi closes that gap: every guest who signs in on your splash page and accepts marketing is created as a customer in your Pepper account, with their name, email address and marketing consent recorded, ready for your Pepper campaigns, offers and loyalty.

Setup uses credentials issued by Pepper. Pepper does not expose API credentials in a self-service screen, so you email your Pepper account manager, or support@pepperhq.com, and ask for API access for a CRM integration that will create customers; Pepper issues an Application ID and an API Token per merchant account. Paste both into the CaptiFi Integrations page for the venue, click Save, then Test connection, which calls Pepper with your credentials so a value that has not been activated yet is caught immediately rather than failing silently later. The API Token can be replaced at any time by saving a new one. If you are not sure who to ask at Pepper, CaptiFi support can liaise with them and complete the connection for you. The CaptiFi side takes about five minutes.

Consent is built in from the start. Only guests who accept marketing are ever sent to Pepper, and their consent is recorded on the customer record, so the guest data Pepper holds stays permission-based. Enabling is not retrospective: only guests who connect after you switch a venue on are sent. Each venue carries its own Pepper credentials, so a group can run several Pepper merchants from one CaptiFi account. As of August 2026 the integration is live, configured from the Integrations page in either CaptiFi dashboard, and available on the Growth plan and above, with the 30-day free trial running at Growth level.

What you get

Why connect Pepper to CaptiFi

Walk-ins join your Pepper customer base

Pepper already holds the guests who order through your app. With CaptiFi connected, guests who only join the WiFi land in the same customer base, so the venue finally sees the visitors who never downloaded the app.

Guests appear within minutes

Every opted-in WiFi guest is created in Pepper within minutes of signing in, with name, email address and marketing consent recorded, with no exports, no imports and no Zapier tasks.

Consent recorded from the first touch

Only guests who accept marketing are ever sent, and their consent is recorded on the Pepper customer record, keeping your Pepper campaigns aligned with GDPR and PECR.

One account, several Pepper merchants

Each CaptiFi venue carries its own Application ID and API Token, so a group can point different venues at different Pepper merchant accounts and roll the integration out site by site.

What data flows to Pepper

Guest name captured at WiFi sign-in

Guest email address captured at WiFi sign-in

Marketing opt-in consent, recorded on the Pepper customer record

Nothing else: guests are routed to the right Pepper merchant by which venue's credentials perform the sync, not by extra fields on the record

How it works

Up and running in minutes

Ask Pepper for API access

Email your Pepper account manager, or support@pepperhq.com, and ask for API access for a CRM integration that will create customers. Pepper issues an Application ID and an API Token per merchant account; there is no self-service credentials screen. CaptiFi support can make this request with Pepper on your behalf.

Paste the credentials into CaptiFi

On the Integrations page in your CaptiFi dashboard, open the Pepper card. The panel shows one section per venue you manage; paste the Application ID and API Token for each venue you want connected. Both fields are required.

Save, then Test connection

Click Save, then Test connection. The test calls Pepper with your credentials, so a value that has not been activated yet is caught immediately rather than silently failing later.

Switch the venue on

The venue reads Connected but paused until you flip the toggle to Enabled. Enabling is not retrospective: only guests who connect after you switch the venue on are sent to Pepper.

Prove it end to end

Forget the WiFi on a phone, reconnect, and complete the splash page with a real email address, accepting marketing. Search your Pepper customer base for that email: within a few minutes the customer appears with marketing consent recorded.

Read the Pepper setup guide

Step by step, with screenshots.

In the real world

How venues use Pepper with CaptiFi

Cafe

A cafe running order at table through its Pepper app captures every walk-in who joins the WiFi, so guests who never downloaded the app still land in the Pepper customer base, ready for the offer that turns them into app users.

Pub

A pub group with several sites gives each venue its own Pepper credentials, so WiFi sign-ins feed the right Pepper merchant and every site's customer base reflects its own footfall.

Restaurant

A restaurant using Pepper loyalty enrols WiFi guests with consent already recorded, so its next Pepper campaign reaches the lunchtime crowd who joined the WiFi as well as the regulars who order through the app.

FAQs

Frequently asked questions

Is the Pepper integration native or does it use Zapier?

It is native. CaptiFi talks to Pepper directly, server-side, using the Application ID and API Token Pepper issues for your merchant account. There is no Zapier account, no Zaps and no task limits involved. As of August 2026 the integration is live and configured from the Integrations page in the CaptiFi dashboard.

Where do I get the Application ID and API Token?

From Pepper. Pepper does not expose API credentials in a self-service screen, so email your Pepper account manager, or support@pepperhq.com, and ask for API access for a CRM integration that will create customers. Pepper issues an Application ID and an API Token per merchant account. Treat the token like a password, and replace it in CaptiFi by saving a new value if it is ever rotated. If you are not sure who to ask, CaptiFi support can liaise with Pepper and complete the connection for you.

What does CaptiFi send to Pepper?

Each opted-in guest is created as a Pepper customer with their name, email address and marketing consent recorded, within minutes of the WiFi sign-in. Guests who decline the marketing opt-in are never sent.

How is guest consent handled?

Only guests who accept marketing on the splash page are ever sent to Pepper, and their consent is recorded on the customer record. Guests who connect to the WiFi but decline marketing never leave CaptiFi, which keeps your Pepper customer base permission-based and your campaigns aligned with GDPR and PECR.

Will guests who connected before I enabled the integration be synced?

No. Enabling is not retrospective: only guests who connect after you flip the venue toggle to Enabled are sent to Pepper. If you want earlier guest data on the Pepper side, export it from CaptiFi (CSV, webhooks or the REST API) and import it into Pepper separately.

We run several venues. Can each connect its own Pepper merchant?

Yes. The configuration panel shows one section per venue you manage, and each venue carries its own Application ID and API Token, so a group can run several Pepper merchants from one CaptiFi account. Each venue also has its own Enabled toggle, so you can roll the integration out site by site.

Which CaptiFi plans include the Pepper integration?

The Pepper integration is available on the Growth plan and above, with no per-integration add-on fees. A 30-day free trial started on Growth or Pro includes it, so you can connect Pepper and watch real guests sync during the trial before you pay anything.

Pairs well with

Square POS Google Reviews Zapier

Start using Pepper with CaptiFi today

30-day free trial. Cancel anytime.

Start Free Trial Browse all integrations

Google, Gmail, Mailchimp, Klaviyo, HubSpot, Salesforce, Facebook, Meta Pixel, Slack, Zapier, Twilio, Tripadvisor, Yelp, Toast, Square, SumUp, Airship, Revinate, Leat, Pepper, EmailOctopus, MailerLite, Incentivio and ChatGPT are trade marks of their respective owners and appear here only to identify the services CaptiFi connects to. CaptiFi is independent of these companies and is not sponsored, certified or endorsed by them. An integration marked coming soon is on our roadmap and is not yet available. Twilio and all related logos are trademarks of Twilio Inc. or its affiliates. Salesforce is a trademark of Salesforce, Inc. Slack is a trademark and service mark of Slack Technologies, Inc., registered in the U.S. and in other countries.