PLG Triggers

PLG Triggers let you respond to specific visitor actions — a video watch, a pricing page visit, a whitepaper download — with Paminga automation, and see exactly how often those actions are occurring.

This page covers connecting PLG Triggers to Actions and viewing performance data. PLG Triggers themselves — name, slug, settings, and how to fire them — are created and managed under Account Settings → PLG Triggers.

There are two ways to fire a PLG Trigger:

• From your website — a single JavaScript call via the Paminga tracking beacon. No contact data required; Paminga identifies the visitor automatically from their session.
• Via the GraphQL API — fire server-side from integrations, mobile apps, or backend pipelines by passing the contact's email address.

Triggering Your Event

Once you've defined a PLG Trigger in Account Settings, fire it from your site with a single JavaScript call:

$__MA.captureEvent('your-event-slug');

No contact data needed — Paminga identifies the visitor automatically from their existing tracking session.

Or fire it server-side via the GraphQL API:

mutation {
  triggerCustomEvent(input: {
    slug: "your-event-slug"
    email: "contact@example.com"
  })
}

For full details — metadata, the timing pattern, all API input fields, and MarketingChannel attribution values — see PLG Triggers Setup.

Configuring Actions

Select an event from the dropdown, then decide what should happen when it fires. You have three tools, and you can use any combination of them:

• Global Actions fire for every contact that triggers the event.
• Conditional Actions fire only when the triggering contact meets segment conditions you define. Use these when your response should differ based on contact attributes, lead score, lifecycle stage, or other criteria.
• An Action Set runs a pre-built, reusable set of actions. You can link one Action Set at a time, and its actions run in addition to any Global and Conditional Actions on the event.

Action Sets work well when you want the same response to fire across multiple triggers — for example, the same nurture enrollment whether a contact submits a form or watches a product video. Global and Conditional Actions are the right choice when the response is specific to this event.

Want visibility without a response yet? Configure no actions. The event is still tracked and still shows up in reporting.

Performance & Reporting

The right panel of the PLG Triggers page shows performance data for the selected event, scoped to the date range you choose.

Metrics

Two metric cards give you a snapshot of the selected period:

• Events Triggered — total number of times the event fired.
• Unique Contacts — the number of distinct contacts who triggered it.

Both show a comparison to the prior period of equal length so you can see whether engagement is trending.

Events by Day

A configurable chart (bar, line, or pie) shows event volume for every day in the range — including days with zero events, so gaps in activity are visible rather than hidden. Click any bar to drill into the contacts behind it.

Contact Drilldown

Clicking a day on the chart (or either metric card for a full-range view) opens a detailed table of individual event triggers. For each contact it shows name, email, company, trigger count, the page URL where the event fired, channel and UTM attribution, and whether the event counted as a conversion.