Tagmango

Overview

TagMango is a third-party payments and subscriptions platform. When someone completes a payment there, TagMango can notify Kraya automatically. Kraya creates or updates a lead using the buyer’s name, email, and phone, and stores the offering name (the product or webinar title from TagMango) on the lead for context.

This is a one-way integration — information flows from TagMango into Kraya. Kraya does not send payment or subscription updates back to TagMango.

There is no TagMango settings page in the Kraya web app. Your webhook address and routing are set up by the Kraya team (or your technical administrator) using internal tools.

What you can do

• Have completed TagMango payments appear as leads in Kraya without manual entry
• See the offering name from TagMango on the lead’s Notes field
• Rely on one lead per phone number per organization — repeat purchases from the same buyer refresh that lead’s details
• Use leads from TagMango everywhere you already use leads: Dashboard, Chrome extension, search, filters, and connected tools such as Zoho integration where applicable

How it works

1. TagMango sends a notification to a unique webhook address that belongs to your Kraya organization.
2. Kraya accepts the request, stores the payload for reference, and processes it shortly afterward (not in the same instant as the HTTP response).
3. If the payment status in the payload is completed, Kraya creates a new lead or updates an existing lead matched by normalized phone number within your organization.
4. The lead gets name, email, and phone from the payload. The dial code and national phone number are combined and normalized so the number is stored consistently.
5. The offering title from TagMango (mangoName) is saved in the lead’s Notes field. If the same buyer pays again, the latest values (including notes) replace the previous ones for that lead.
6. New leads are placed in a default pipeline and stage chosen when the integration was set up. If nothing custom was configured, they go to your standard Leads pipeline at the New Lead stage.
7. Notifications that are not completed, or that fail validation, do not create or update leads, but your Kraya operations team can still review stored payloads if needed.

Step-by-step guide

Getting started (with Kraya support)

1. Ask your Kraya contact to enable TagMango for your organization.
2. They will provide the webhook URL to paste into TagMango’s webhook or integration settings.
3. Complete a test purchase (or wait for a real completed payment).
4. In Kraya, open the Dashboard and search for the buyer by phone or email to confirm the lead.

Changing where new TagMango leads land

If you need new buyers to appear in a specific pipeline and stage (instead of Leads / New Lead), ask your Kraya team to update TagMango routing for your organization. This is not editable from the Kraya web app today.

Settings and configuration

Role-based behavior

• All team members see and work with TagMango-sourced leads like any other lead once they exist in Kraya.
• Connecting TagMango, copying the webhook URL, or changing routing is done by Kraya operations or an authorized technical administrator, not from the standard Kraya UI.

Limits and quotas

• One TagMango connection per organization (one webhook endpoint).
• Processing runs in the background; during busy periods, allow a short delay before a new payment appears as a lead.
• Organizations on the free subscription pack are treated like other inbound lead sources: the webhook still responds successfully, but leads may not be created. If you believe this applies to you, ask Kraya support about your plan.

Common edge cases

• Same buyer, new order Kraya matches by phone. The existing lead is updated (name, email, notes) with the latest payment details. You still have one lead, not one per order.

• Different buyers Different phone numbers always produce or match separate leads.

• Payment status not “completed” The event is acknowledged but no lead change is made for that notification.

• Missing or invalid fields in the payload Kraya may record the attempt but not create or update a lead. Your Kraya team can diagnose using stored payload history.

• Wrong or missing webhook URL in TagMango Events never reach your organization’s integration. Double-check the URL character for character with what Kraya provided.

• Webhook URL shared or leaked The URL acts like a private entry point. If someone else obtained it, they could send unwanted requests. Treat the link as confidential and ask Kraya to rotate the integration if you suspect it was exposed.

Troubleshooting

Completed payments in TagMango but no lead in Kraya

• Cause: Webhook URL mismatch, free-plan restriction, invalid payload, or background processing still in progress.
• Fix: Confirm the exact webhook URL in TagMango, wait a few minutes and search by phone again, then contact Kraya support with the order time and buyer phone number.

Lead exists but Notes or contact details look wrong

• Cause: A newer webhook overwrote fields, or the payload from TagMango contained different data than expected.
• Fix: Compare with the buyer record in TagMango; edit the lead in Kraya if you need corrections.

Unknown or old webhook URL

• Cause: Integration was recreated or the URL was copied incorrectly.
• Fix: Ask Kraya for the current webhook URL registered for your organization.

Decision tree

• If nothing appears after a completed payment → verify URL in TagMango → wait a few minutes → search by phone and email → contact Kraya support.
• If leads appear but in the wrong pipeline → ask Kraya to adjust TagMango routing for new leads.
• If you are on a free plan and expect automatic leads → confirm your subscription with Kraya.

FAQs

• Does Kraya send data back to TagMango? No. It is one-way into Kraya.

• Is the webhook protected by a password? Security relies on a long, unguessable URL. Do not share it publicly.

• Can I pause TagMango lead creation? Remove or change the webhook in TagMango, or ask Kraya support to disable the integration on Kraya’s side.

• Will reconnecting or changing the URL create duplicate leads? No. Matching is by phone number within your organization.

• Where do I see the product or webinar name? In the lead’s Notes field (the value comes from TagMango’s offering name).

Tips and best practices

• Paste the webhook URL into TagMango once and avoid sharing it in chat or email; request a new URL from Kraya if it may have been exposed.
• After go-live, run one test completed payment and verify name, email, phone, and notes in Kraya.
• If multiple teams own different pipelines, agree on the default pipeline and stage for TagMango buyers before going live.

Related features

• Dashboard — find and manage TagMango leads in pipelines and stages
• Import leads — other ways leads enter Kraya
• IndiaMART integration — similar webhook-based lead capture
• JustDial integration — similar slug-based webhook pattern
• Other integrations — integrations without a dedicated dashboard page, including MyOperator
• Zoho integration — if your organization syncs leads to Zoho, new TagMango leads follow the same rules as other sources

Screenshots