Skip to main content

 –

Understanding the Detect/Trigger services

Suggest edit Updated on November 16, 2021

The Detect/Trigger set of services are used to detect whether a customer’s device has tripped a Geofence in the system and to trigger Events associated with tripped Geofences. These services support handling requests for multiple customers in a single request.

The following two variants of the service exist:

  • HandleMktGeolocations HTTP Service

    http://<host>:<port>/prweb/PRHTTPService/PegaMKTGeolocation/Services/HandleMktGeolocations?CustomerID=<CustomerID1,2,..n>&DeviceID=<DeviceID1,2,..n>&DeviceLatitude=<DeviceLatitude1,2,..n>&DeviceLongitude=<DeviceLongitude1,2,.n>

    When using this service for multiple customers, ensure that each of the values are comma-separated (e.g. CustomerID=A1,A2,B1) and that the length of each of the request fields (such as CustomerID, DeviceLatitude, etc.) is the same.

  • HandleMktGeolocations SOAP Service

    The following URL provides the WSDL for your this service: http://<host>:<port>/prweb/PRSOAPServlet/SOAP/PegaMKTGeolocation/Services?WSDL

    The following is an example SOAP request for two customers:

    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:geol="GeolocationPayload">  <soap:Header/>  <soap:Body>    <geol:GeolocationPayload>      <Geolocation>        <CustomerID>JR</CustomerID>        <DeviceID>ANDR1234</DeviceID>        <DeviceLatitude>41.34</DeviceLatitude>        <DeviceLongitude>-71.79</DeviceLongitude>      </Geolocation>      <Geolocation>        <CustomerID>RA</CustomerID>        <DeviceID>IO12</DeviceID>        <DeviceLatitude>41.797</DeviceLatitude>        <DeviceLongitude>-72.077</DeviceLongitude>      </Geolocation>    </geol:GeolocationPayload>  </soap:Body></soap:Envelope>

    Both variants of this service expect the following inputs:

    • CustomerID – Customer identifier
    • DeviceID – Device identifier
    • DeviceLatitude – Latitude of the device
    • DeviceLongitude - Longitude of the device

For each customer location, the system evaluates whether the location trips any of the defined Geofences. For each Geofence that is tripped, the system triggers all Events associated to that Geofence.

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us