Actito

Connect Apple Wallet and Google Wallet to Actito (CRM / marketing automation) with The Wallet Crew. Create, update, and notify wallet passes from Actito scenarios.

This integration connects Actito scenarios to Apple Wallet and Google Wallet through The Wallet Crew.

Actito decides who, when, and what. The Wallet Crew runs the wallet layer.

Actito is where segmentation, personalization, and customer journey orchestration happen. The Wallet Crew turns those journeys into a wallet pass that stays visible and useful.

This is more than “one more channel” next to email, SMS, and app push. It is a way to put the right information in the customer’s pocket, exactly when needed. For teams looking at how to connect Apple Wallet and Google Wallet to Actito CRM, this integration is the practical answer.

This becomes essential for loyalty, membership, gift cards, and offers.

Actito orchestrates “who/when/what”. The Wallet Crew executes everything wallet-side: pass creation, updates, notifications, and animations.

What this unlocks

• A persistent touchpoint. The pass lives in Apple Wallet or Google Wallet.

• Real-time utility. The pass is updated when the customer situation changes.

• Less friction. No app install required to deliver value.

• Better orchestration. Actito scenarios automate wallet moments.

• Stronger targeting. Wallet events feed back into Actito for smarter timing.

Real-world examples

• Retail loyalty: after purchase, update points and tier on the pass. Then notify when a reward unlocks.

• Membership: when status changes (active, paused, renewed), refresh the pass instantly. Use a notification only for key moments.

• Offers: add a new coupon or benefit to the pass. Notify close to expiry to drive redemption.

• Events: push last-minute changes (schedule, venue, gate info). Reduce no-shows with day-of reminders.

Thanks to The Wallet Crew connectors and its multi pass data provider architecture, wallet scenarios can be orchestrated from Actito while other pass data providers keep contributing. This gives the best of both worlds. The Wallet Crew can display information from all systems (Cegid, Secutix, etc) on the same pass and merge them, without sync issues.

What this integration does

Connect Actito to The Wallet Crew to:

1. Update passes from Actito scenarios (Journey Builder custom actions). Keep loyalty points, tier, coupons, balance, or store info up to date.

2. Trigger wallet notifications (push/messages) for a given pass from Actito scenarios. Nudge at the right moment without relying only on email open rates.

3. Sync Actito profile changes into The Wallet Crew (webhooks). Keep wallet content aligned with consent, preferences, and profile data.

4. Sync The Wallet Crew events back to Actito (webhooks). Track events like customer creation and wallet installation status.

Usage

Send a push notification

Use the neostore send message custom activity inside an Actito scenario.

It sends a push-style wallet message to the customer’s pass. On Apple Wallet, it appears on the lock screen. On Google Wallet, it is displayed on the pass.

For more details about wallet notifications, see Push notifications.

Use it for time-sensitive moments. Keep it rare.

Real-world examples

• Retail loyalty: “You’ve unlocked a reward.” Update points/tier. Then notify.

• Offer expiry: “Your coupon expires tonight.” Write the coupon to the pass. Then notify.

• Click & collect: “Your order is ready.” Show pickup info on the pass. Then notify.

• Membership: “Renewal in 3 days.” Update expiry and status. Notify only if needed.

New profile & profile update synchronization

When an Actito profile is created or updated, the connector automatically refreshes the customer’s wallet pass.

This keeps the pass aligned with the latest profile data, without building extra “update pass” branches in every scenario.

This is a key feature. If the pass is connected to multiple data providers (Cegid, Comarch, …), a profile change in Actito triggers a refresh that reconciles data from all providers.

Real-world examples

• Data hygiene: a customer fixes their name or email in the brand preference center. The pass updates on the next refresh.

• Store preference: a customer changes their preferred store. The pass updates to show the right store address and map link.

• Multi-system loyalty: Actito profile changes (segment, tier label, custom attributes) refresh the pass while points still come from the loyalty provider.

Wallet installation status synchronization

When a customer installs or uninstalls a pass, the connector syncs that status back to Actito.

Actito stores this in the neostore_wallets table. Use it as a deterministic signal for segmentation and scenario branching.

Install and uninstall events can also trigger follow-ups or rewards.

Real-world examples

• Scenario branching: if the pass is installed, send a wallet notification. If not, send an email/SMS with an “Add to Wallet” link.

• Onboarding reminder: if the pass isn’t installed after 24 hours, send a nudge.

• Suppression: stop “add to wallet” messages once the pass is installed.

• Reward on install: when the pass is installed, grant +10 loyalty points or unlock a welcome perk.

• Win-back: when a pass is uninstalled, trigger a light reactivation flow with a new link.

Pass Data Provider

Use Actito as a data source for the pass.

This lets The Wallet Crew display Actito profile attributes on the pass, like first name, last name, tier label, or any custom field stored in Actito.

Real-world examples

• Loyalty: show the customer’s tier label coming from Actito segmentation.

• Membership: display member name and status, synced from the Actito profile.

• Personalization: show a preferred store, language, or a “next best offer” field maintained in Actito.

Advanced configuration

Use the extensions.actito.profile.mapper extensibility endpoint to control which Actito attributes are read and how they are mapped into The Wallet Crew account object.

By default, the connector maps firstName and lastName.

/**
 * Enhanced default mapping from Actito profile to the wallet crew
 *
 * @param {Object} data - Attributes coming from Actito
 * @param {Object} account - The wallet crew account object to populate (mutated in place)
 */
function mapFromActito(data, account) {
  // Example showing default mapping
  if(data["firstName"]) {
    account["firstName"] = data["firstName"];
  }
  if(data["lastName"]) {
    account["lastName"] = data["lastName"];
  }
}

export default function (context) {
  context.register('extensions.actito.profile.mapper', {
    MapFromActitoProfiles: mapFromActito
  });
}

Setup

The Wallet Crew Configuration

1

Enable connector

Ask The Wallet Crew team to enable the Actito connector for the target environment.

2

Configure general settings

Open the Actito connector settings in The Wallet Crew back-office.

Open Actito General settings page

Check that the server, entity, and identifier fields match the Actito environment and data model.

Fill in the form with the following information:

Server	URL of the Actito server
API Key	Actito API key that lets The Wallet Crew access the Actito environment.
Entity	The name of the environment (license name) within Actito
Profile Table Name	Name of the Actito table that stores profiles (customer information)
Actito External Identifier	Name of the column that contains the customer identifier. This column lets The Wallet Crew bind a pass to a specific customer.
Pass external Identifier	Name of the external identifier key within The Wallet Crew.

The Actito External Identifier and Pass External Identifier must refer to the same value.

Example: if the pass is also connected to Cegid, use the Cegid Y2 customerId. In that case, set Pass external Identifier to y2.customerId.

Get these values from Actito (API settings) and from the Actito data model (table + identifier column).

3

Configure wallet template

To show Actito messages on the pass, add a field in the pass template.

When a message is sent, the connector stores it in additionalData.actito_message.

Apple Wallet

Add a back field with the following settings:

Label	Message
Value	{{ additionalData.actito_message }}
Change Message	%@

Confirm the back field value and change message match the Actito message key.

Google Wallet

Add a back field with the following settings:

Header	Message
Value	{{ additionalData.actito_message }}

Confirm the header and value match the Actito message key on the Google Wallet side.

Once setup is complete, the connector automatically creates the required tables and custom actions in Actito.

FAQ

What does Actito do vs what does The Wallet Crew do?

Actito decides who, when, and what in scenarios.

The Wallet Crew runs the wallet layer: pass creation, updates, and notifications.

Customers don’t need an app. They add a pass to Apple Wallet or Google Wallet.

What can be automated from Actito scenarios?

• Update pass content (points, tier, balance, expiry, store info, custom fields).

• Send a wallet message with neostore send message.

• Refresh passes automatically when Actito profiles change.

• Branch by install status using neostore_wallets (notify vs email/SMS).

How is pass installation tracked?

Install/uninstall status is synced into Actito in the neostore_wallets table.

Use it for segmentation, suppression, and scenario branching.

What about consent and GDPR?

Make wallet messages conditional on consent, especially for marketing.

See Consents & GDPR compliance.