Tracks a conversion event (in other words, an action a user takes) for a user. Logs an error message if the specified event key doesn't match any existing events.
SDK 3.7 and higher
Use this method to track events across multiple flag rules for a user. You should only make one track call per conversion (i.e., user action), even if many rules are measuring the conversion.
You call the Track Event method on a user. For more information about the user object, see OptimizelyUserContext.
The attributes passed to Track Event are only used for results segmentation.
This table lists the required and optional parameters for the Track Event method.
The key of the event to be tracked. This key must match the event key provided when the event was created in the Optimizely app.
A map of key-value pairs specifying tag names and their corresponding tag values for this particular event occurrence. Values can be strings, numbers, or booleans.
These can be used to track numeric metrics, allowing you to track actions beyond conversions, for example: revenue, load time, or total value. See details on reserved tag keys.
This method sends conversion data to Optimizely. It doesn't provide return values.
$user = $optimizely->createUserContext('user123'); $tags = [ "category" => "shoes", "purchase_count" => 2 ]; $user->trackEvent("my_purchase_event_key", $tags);
The table lists other Optimizely functionality that may be triggered by using this method.
Calling this method records a conversion and attributes it to the variations that the user has seen.
You can create metrics on this conversion event and add metrics to experiments even after the conversion has been tracked.
For more information, see the paragraph Events are always on in the introduction of Events: Tracking clicks, pageviews, and other visitor actions.
Accessing this method triggers a call to the
Important! This method won't call the
The language/platform source files containing the implementation for PHP is Optimizely.php.
Updated 6 months ago