Jobiqo now offers a consent-free way to capture key user events (e.g. job apply start) as well as machine-generated events (e.g. job publish), providing a complementary solution to the existing cookie-based Jobiqo Analytics setup.
How does it work?
Jobiqo SSA is relying on the Google Measurement Protocol API to submit events directly to a dedicated Google Analytics 4 property.
Why is user consent not required?
Consent is not required for Jobiqo SSA since neither user-sensitive data is passed along with the events, nor a direct TCP connection between the website visitor and Google Analytics is established.
In contrast, in a standard Google Analytics setup (used by the Jobiqo Analytics system), a direct connection between the website user and Google Analytics is established (see chart below), which requires consent.
Why do I need Jobiqo SSA?
The main difference between Jobiqo SSA and cookie-based Google Analytics 4, is that Jobiqo SSA does not require a user’s consent to work.
The main purpose of the SSA is to capture the same custom events as in the standard Jobiqo Analytics setup and to close the “consent gap”. This means that for important user events, such as job visits or job applications, SSA enables you to capture every event and not “lose” events due to missing consent from a user.
Additionally, certain events which are fully or partially machine-generated, for example, the job publish event (which in the majority of cases are triggered by an imported feed), can now reliably be tracked.
Can Jobiqo SSA then replace the standard GA4?
Jobiqo SSA is not seen as a replacement, but rather a complementary solution to the standard cookie-based Google Analytics 4.
This has several reasons, but mainly there are some specific limitations in Google Measurement API and the way we currently have implemented Jobiqo SSA.
First and foremost, we do not track user-specific data. This means that no events can be tied to a specific user in any way. The typical Google Analytics information about where a user came from (e.g. source, medium, campaign, device, browser, location etc.) is also not captured.
Additionally, the Jobiqo SSA events are all submitted as “individual” events. This means that it is not possible to string together events into sessions or to attribute two or more events directly to each other.
In short, analyzing acquisition data and user behaviour based on the dimensions mentioned above would still need to take place based on the cookie-based Google Analytics 4 data.
Which events are captured?
Currently, the following events are being captured using the Jobiqo SSA:
| # | Metric Name | Description |
| 1 | ss_job_alert_prompt | Triggered after a sign up modal had been shown to the user. |
| 2 | ss_job_alert_signup | Triggered after a user signed up to a job alert. |
| 3 | ss_job_alert_signup_anonymous | Triggered after an anonymous user had signed up to a job alert. |
| 4 | ss_job_apply_complete | Triggered after the user submit an internal application. |
| 5 | ss_job_apply_start | Triggered after the user clicked the apply button. |
| 6 | ss_job_bookmark | Triggered after a user bookmarks a job. |
| 7 | ss_job_edit | The job edit is displayed right after the recruiter finishes editing a job. |
| 8 | ss_job_publish | Triggered after a job is published or republished (server-side). |
| 9 | ss_job_search | Triggered after a user searches for jobs on a job search page. |
| 10 | ss_job_visit | Triggered when the job detail is displayed (split-screen or single) to an applicant. |
| 11 | ss_login | Triggered after a user successfully logged in. |
| 12 | ss_orgprofile_visit | Triggered after a user visits an organization profile page. |
| 13 | ss_qa_basic_info_page_view | Quick apply: This event is triggered when the contact information page is viewed. |
| 14 | ss_qa_file_upload_page_view | Quick apply: This event is triggered when the file uploads page is viewed. |
| 15 | ss_qa_questions_page_view | Quick apply: This event is triggered when the questions page is viewed. |
| 16 | ss_qa_review_info_page_view | Quick apply: This event is triggered when the review page is viewed. |
| 17 | ss_qa_success_page_view | Quick apply: This event is triggered when the success page is viewed. |
| 18 | ss_resume_completed | Triggered after an applicant fills out all the required fields of their resume. |
| 19 | ss_sign_up | Triggered after a user verified their account. |
| 20 | ss_sign_up_start | Triggered after a user created their account. |
| 21 | ss_view_original_ad_btn_click | Triggered when the "View original ad" button is clicked on a job. |
| 22 | ss_order_complete | Triggered when job/self-service order is paid and completed. |