Embedding Whereabouts Tracking on Profile Pages

Embedding Whereabouts Tracking Script on Pages Built Using the WA API

Whereabouts widgets have their own light-weight user tracking built in, but if you've built any additional pages using the Whereabouts API, you must manually add tracking to those pages:

<code><script> !function(t,e){var o,n,p,r;e.__SV||(window.posthog=e,e._i=[],e.init=function(i,s,a){function g(t,e){var o=e.split(".");2==o.length&&(t=t[o[0]],e=o[1]),t[e]=function(){t.push([e].concat(Array.prototype.slice.call(arguments,0)))}}(p=t.createElement("script")).type="text/javascript",p.crossOrigin="anonymous",p.async=!0,p.src=s.api_host.replace(".i.posthog.com","-assets.i.posthog.com")+"/static/array.js",(r=t.getElementsByTagName("script")[0]).parentNode.insertBefore(p,r);var u=e;for(void 0!==a?u=e[a]=[]:a="posthog",u.people=u.people||[],u.toString=function(t){var e="posthog";return"posthog"!==a&&(e+="."+a),t||(e+=" (stub)"),e},u.people.toString=function(){return u.toString(1)+".people (stub)"},o="init capture register register_once register_for_session unregister unregister_for_session getFeatureFlag getFeatureFlagPayload isFeatureEnabled reloadFeatureFlags updateEarlyAccessFeatureEnrollment getEarlyAccessFeatures on onFeatureFlags onSessionId getSurveys getActiveMatchingSurveys renderSurvey canRenderSurvey getNextSurveyStep identify setPersonProperties group resetGroups setPersonPropertiesForFlags resetPersonPropertiesForFlags setGroupPropertiesForFlags resetGroupPropertiesForFlags reset get_distinct_id getGroups get_session_id get_session_replay_url alias set_config startSessionRecording stopSessionRecording sessionRecordingStarted captureException loadToolbar get_property getSessionProperty createPersonProfile opt_in_capturing opt_out_capturing has_opted_in_capturing has_opted_out_capturing clear_opt_in_out_capturing debug".split(" "),n=0;n<o.length;n++)g(u,o[n]);e._i.push([i,s,a])},e.__SV=1)}(document,window.posthog||[]); const validPaths = ['/events/','/event/','/operators/','/operator/','/listing/','/listings/']; const currentPath = window.location.pathname; const shouldInitPosthog = validPaths.some((path) => currentPath.includes(path)); if (shouldInitPosthog) {   const pathParts = currentPath.split('/').filter(Boolean);   const recordedId = pathParts[pathParts.length - 1];   const properties = { organizationId: '<YOUR_ORGANIZATION_ID>' };   if (currentPath.includes('/event/') || currentPath.includes('/events/')) {     properties.eventId = recordedId;   } else {     properties.operatorEntityId = recordedId;   }   posthog.init('<POSTHOG_API_KEY>', {     api_host: '<POSTHOG_API_HOST>',     name: 'whereabouts-integration-<YOUR_ORGANIZATION_ID>',     persistence_name: 'whereabouts-integration-<YOUR_ORGANIZATION_ID>'   });   posthog.capture('expanded-details-pageview', properties); } </script>

To use this tracking script, you'll need to obtain the following values from your developer:

  • <YOUR_ORGANIZATION_ID>: Your organization's Whereabouts ID
  • <POSTHOG_API_KEY>: PostHog project API key
  • <POSTHOG_API_HOST>: PostHog instance host URL
  • <YOUR_POSTHOG_NAME>: whereabouts-integration-${YOUR_ORGANIZATION_ID}

Replace these placeholders in the script with the actual values provided by your developer. The script will automatically track page views and relevant IDs for event and operator pages. Depending on your use-case, you may need to retrieve these variables using different methods. Common methods include environment variables and URL parameters.

Still need help? Contact Us Contact Us