Sometimes you need to track an event, but there is no way to set a trigger. This can be due to an inappropriate architecture of the application or simply because you can not install the fusedeck script at all.
The good news is: You can still fire your events, even from an external domain. This is done via a pixel or redirect call.
<img src="https://io.fusedeck.net/t/event.gif?propertyId=PROPERTY_ID&eventId=1" />
If you need to transfer more data to the endpoint you can use the PAYLOAD parameter. This accepts an encoded JSON.
Example transport payload to fusedeck
{
propertyId: PROPERTY_ID,
eventId: EVENT_ID,
adId: AD_ID,
siteId: SITE_ID,
values:{
firstname: "Fuse",
name: "Deck"
}
}
<img src="https://io.fusedeck.net/t/event.gif?payload=ENCODED_JSON" />
💡 Make sure the PROPERTY_ID & EVENT_ID is set correctly. Optional AD_ID and SITE_ID
⚠️ This does not transfer the Campaign Information. Use the Helper Version for campaign context
https://io.fusedeck.net/t/event.gif?payload={%22propertyId%22:%22mgKxAyimB8%22,%22eventId%22:%22496340%22,%22values%22:{%22meinName%22:%22Micha2000%22}}
This will not work:
https://io.fusedeck.net/t/event.gif?propertyId=mgKxAyimB8&eventId=496340&payload={%20meinName:%27Theo%27%20}
If redirect instead of a pixel is needed, this endpoint can be used. The endpoint will fire the event and redirect to the defined redirect 'r'
https://io.fusedeck.net/t/goto?r=https%3A%2F%2Fcapturemedia.ch&payoad=ENCODED_JSON
If you need to transfer more data to the endpoint you can use the PAYLOAD parameter. This accepts an encoded JSON.
{
propertyId: PROPERTY_ID,
eventId: EVENT_ID,
adId: AD_ID,
siteId: SITE_ID,
values:{
firstname: "Fuse",
name: "Deck"
}
}
💡 Make sure the PROPERTY_ID & EVENT_ID is set correctly. Optional AD_ID and SITE_ID