Send in-app purchase events to Zendesk
Bring current subscription and purchase context into the support conversation.
Instead of asking a customer to explain what they bought or whether a plan is active, agents can check the linked customer record directly from the ticket.
Why subscription context matters in support
Support conversations often stall because the agent cannot tell whether a customer is subscribed, what they purchased, or when a plan renews. This integration surfaces that context inside Zendesk, helping teams answer billing and access questions with current data rather than relying on the customer to recall details.
What agents see inside a ticket
Open a ticket and the linked customer information appears in the conversation. Agents can review subscription status, purchase history, and account details instantly, then use that record to decide whether the issue involves an active plan, a renewal, a past purchase, or a custom attribute set on the account.
How customer matching works
Matching starts with the ticket requester. The integration automatically links Zendesk ticket requesters to the corresponding customer profile. If the ticket email does not produce a match, an agent can manually identify the correct customer using an ID or email. Treat that manual step as a verification checkpoint: confirm the identifier belongs to the person who opened the ticket before relying on the displayed history.
A practical triage checklist
Use this checklist when triaging a subscription-related ticket: 1) Confirm the requester is matched to the correct customer. 2) Check active subscriptions and renewal information. 3) Review the latest purchases for purchase-history context. 4) Look for custom attributes that may explain access, billing, or account state. 5) If no match was found, search manually by ID or email and re-check before responding.
Beyond the ticket view
The same data layer can feed other tools through no-code integrations, connecting real-time events and revenue data across the stack. That makes Zendesk one view of the customer record rather than a separate manual lookup.
| Ticket question | Where to check | What it helps decide |
|---|---|---|
| Is the customer currently subscribed? | Subscription status and active subscriptions | Whether access or billing help is needed |
| When does the plan renew? | Renewal information | Whether timing explains the issue |
| What did they buy before? | Latest purchases and purchase history | Whether a past purchase is relevant |
| Is there account-specific context? | Custom attributes and account details | Whether a stored attribute explains the case |
Based only on data types named in the captured source; no additional fields are claimed.
Frequently asked questions
Does the integration match a ticket requester to a customer automatically?
Yes. When a ticket arrives, the integration attempts to link the requester to the matching customer profile automatically, so the agent can see relevant subscription information without leaving the ticket.
What if automatic matching does not find the right customer?
You can look the customer up manually using an ID or an email address. That fallback is useful when the ticket email does not produce an automatic match.
What subscription information can an agent see in Zendesk?
The ticket view can show subscription status and renewal information, active subscriptions, revenue and product information, purchase history, account details, and any custom attributes assigned to the customer.