Carticy Conversions exposes a small, stable set of hooks for developers. Add the snippets below to your theme’s functions.php or a small custom plugin.

Filters

carticy_conversions_consent_signals

Filter the array of consent signals the plugin considers when deciding whether a tag may fire. Use this to feed consent from a source the plugin doesn’t natively detect.

add_filter( 'carticy_conversions_consent_signals', function ( array $signals ) {
    // Inspect or augment the detected consent signals.
    return $signals;
} );

carticy_conversions_wp_consent_api_is_explicit

Controls whether consent obtained via the WP Consent API is treated as explicit. Receives the current boolean and the consent $categories.

add_filter( 'carticy_conversions_wp_consent_api_is_explicit', function ( $is_explicit, $categories ) {
    return $is_explicit;
}, 10, 2 );

carticy_conversions_generic_consent_presets

Filter the registry of built-in CMP presets, so you can register a preset for a consent platform that isn’t included out of the box.

add_filter( 'carticy_conversions_generic_consent_presets', function ( array $presets ) {
    return $presets;
} );

carticy_conversions_generic_consent_browser_adapters

Filter the browser-side adapters used to read consent state from the visitor’s browser for the generic consent integration.

add_filter( 'carticy_conversions_generic_consent_browser_adapters', function ( array $adapters ) {
    return $adapters;
} );

Actions

carticy_conversions_internal_event_created

Fires whenever the plugin records an internal tracking event. Receives the $event and the $destination_key it is bound for, which is handy for logging or forwarding events to your own pipeline.

add_action( 'carticy_conversions_internal_event_created', function ( $event, $destination_key ) {
    // React to a recorded tracking event.
}, 10, 2 );

carticy_conversions_missing_client_purchase_event

Fires when a purchase was expected to produce a client-side event but none was recorded. Receives the $order_id and the $event_id, which is a useful place to hang custom alerting on tracking gaps.

add_action( 'carticy_conversions_missing_client_purchase_event', function ( $order_id, $event_id ) {
    // Alert or reconcile a missing client-side purchase event.
}, 10, 2 );

carticy_conversions_fs_loaded

Fires once the Freemius licensing SDK has loaded, for code that needs to interact with the licensing layer safely after initialization.

add_action( 'carticy_conversions_fs_loaded', function () {
    // Licensing SDK is ready.
} );

The debug log

Enable the carticy_conversions_debug_log option (Settings → Advanced) to write a detailed dispatch trail to WooCommerce → Status → Logs under the source carticy-conversions. This is the fastest way to see exactly why a given order was or wasn’t sent to each destination.