> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# New Feature: Conditional Firing Rules for Partner Platform Integrations

> Define precise criteria directly in your integration tiles to control exactly when Invoca sends data to a partner — without relying on operational Signals or manual lookup tables.

Previously, routing call data based on location or consent required workarounds like "operational" Signals or manual Lookup Tables. Conditional Firing Rules let you define that logic directly within an integration action.

## Why use Conditional Firing Rules

* **Simplified consent management** — block data from reaching a specific partner (like Meta or Google) when a consumer has opted out, supporting GDPR, CCPA, and similar requirements
* **Seamless multi-location routing** — for franchise or multi-brand accounts, route data to the correct account or property based on location IDs or brand attributes, without hundreds of "outcome" Signals
* **Cleaner reporting** — eliminate operational Signals that exist only to trigger an integration, keeping Signal reports focused on real business outcomes
* **Self-service control** — manage complex data flows yourself through a familiar interface, without needing custom support

## How it works

Conditional Firing Rules use the same logic-builder interface as Invoca Signals and Scorecards, built directly into the action configuration workflow. You can build rules based on:

* Marketing Data (for example, store\_id, UTM parameters, or custom data layer attributes)
* Campaign Names
* Profile Names

If a trigger event doesn't meet the defined conditions, the integration simply doesn't fire for that event.

## Common use cases

**Honoring consumer consent:** if your Invoca Tag captures a consent flag from your Consent Management Platform, you can require, for example, that `cookie_consent` is not `denied` before an integration fires — keeping data from reaching downstream platforms when a user has opted out.

**Multi-location data routing:** for a franchise or multi-brand account, create an integration action that only fires when `store_id` equals a specific value — so each location or franchisee receives only its own lead data, with clean attribution.

## Availability

Conditional Firing Rules are currently available for all Partner Platform (PPMC-powered) Actions. Support for Custom Webhooks and Connect Apps is planned for a future release.

## Where to go next

* [API Integrations: Conditional Firing Rules](/s/article/api-integrations-conditional-firing-rules)
* [Connect Apps & No-Code Integrations](/s/article/connect-apps-and-no-code-integrations)