Using WordPress Hooks in Influenzic

Influenzic exposes WordPress action and filter hooks throughout its codebase following standard WordPress conventions. This means you can modify virtually any platform behaviour without editing plugin core files. All Influenzic hook names use the inzc_ prefix.

Actions vs Filters

• Actions (add_action) — run your code at a specific point in the execution flow. Return value is ignored.
• Filters (add_filter) — modify a value before it is used. You must return the value.

// Action: run code when a project is created
add_action( 'inzc_project_created', function( $project_id, $campaign_id, $user_id ) {
    error_log( 'Project created: ' . $project_id );
}, 10, 3 );

// Filter: modify the platform commission rate
add_filter( 'inzc_get_commission_pct', function( float $rate ): float {
    // Zero commission for the first 30 days (launch promotion)
    $diff = ( time() - (int) get_option( 'inzc_launch_timestamp', time() ) ) / DAY_IN_SECONDS;
    return $diff <= 30 ? 0.0 : $rate;
} );

Where to Add Hooks

Add your hooks in one of these locations — never edit plugin core files:

• A custom plugin — recommended; hooks survive theme changes and can be version-controlled independently
• Child theme functions.php — acceptable for small site-level tweaks
• A mu-plugins file — for hooks that must run before all plugins on every request

Priority

The third argument to add_action/add_filter is the priority (default 10). Lower numbers run earlier. Use priority > 10 to run after Influenzic’s own internal hooks on the same action; use priority < 10 to run before.

Key Action Hooks

Key Filter Hooks