You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that your Pixel through GTM is correctly initialized, it's time to send some events.
287
-
Sadly the parameters between the Conversions API and Facebook Pixel are not identical, so they must be mapped to the [correct format](https://developers.facebook.com/docs/meta-pixel/reference).
288
288
An easy way of doing this is by extending the `FacebookAds\Object\ServerSide\Event` class and implementing the `Esign\ConversionsApi\Contracts\MapsToDataLayer` interface on it:
289
289
```php
290
290
use Esign\ConversionsApi\Contracts\MapsToDataLayer;
Copy file name to clipboardExpand all lines: UPGRADING.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,4 +16,5 @@ See the [docs](README.md#creating-event-classes) for an example on this.
16
16
In case you're using the Facebook Pixel directly, use `<x-conversions-api-facebook-pixel-page-view />`.
17
17
If you're sending them through Google Tag Manager, use `<x-conversions-api-data-layer-page-view />`.
18
18
Note that the dataLayer variable name has been changed from `conversionsApiEventId` to `conversionsApiPageViewEventId`.
19
-
- The `@conversionsApiFacebookPixelScript` directive has been replaced with `<x-conversions-api-facebook-pixel-script />`.
19
+
- The `@conversionsApiFacebookPixelScript` directive has been replaced with `<x-conversions-api-facebook-pixel-script />`.
20
+
- The `@conversionsApiDataLayer` has been removed. Support for dataLayer events is possible through `<x-conversions-api-data-layer-variable :event="$event" />` or `<x-conversions-api::data-layer-variable :arguments="[]" />`. See the [docs](README.md#google-tag-manager) for an example on this.
0 commit comments