Other Methods¶
There are additional methods available within the SDK for supporting specific use cases. You can discuss your use case and integration approach with Pulse account executive or support@pulseid.com.
Custom Positioning¶
You can use custom positioning technologies for your use case with Pulse's Campaign targeting and Analytics capabilities.
- When user enters a monitored region, use the
enteredRegionmethod in Pulse SDK to pass the region information. You also need to specify the positioning technology used for monitoring usingpulseRegion.typeso appropriate Campaigns can be targeted. You can also give a custom location so by passingCLLocationalong with the region. For e.g.:
PulseRegion *pulseRegion = [PulseRegion regionWithId:@"9f934102-a9a2-4cf8-85a1-844b66c3fc09"];
pulseRegion.type = PL_GEOMAGNETIC_REGION;
[[PulseSDK sharedClient] enteredRegion:pulseRegion location:(CLLocation*)];
let pulseRegion = PulseRegion.init(id: "9f934102-a9a2-4cf8-85a1-844b66c3fc09")
pulseRegion?.type = RegionType.PL_GEOMAGNETIC_REGION
PulseSDK.sharedClient().enteredRegion(pulseRegion,CLLocation?)
- When the user leaves the monitored region, use the
exitRegionmethod in Pulse SDK to pass the region and the custom location. For e.g.:
PulseRegion *pulseRegion = [PulseRegion regionWithId:@"9f934102-a9a2-4cf8-85a1-844b66c3fc09"];
pulseRegion.type = PL_GEOMAGNETIC_REGION;
[[PulseSDK sharedClient] exitedRegion:pulseRegion location:(CLLocation*)];
let pulseRegion = PulseRegion.init(id: "9f934102-a9a2-4cf8-85a1-844b66c3fc09")
pulseRegion?.type = RegionType.PL_GEOMAGNETIC_REGION
PulseSDK.sharedClient().exitedRegion(pulseRegion,CLLocation?)
Enter and Exit
Every enteredRegion call needs to have a corresponding exitedRegion call. This is to prevent false enter events and the Platform to deliver Campaigns and Analytics correctly.