# Sponsorship Page Views & Search Tracking
Page view event is a page_view direct rule in Launch.
Search event is a child_search_result_click direct rule in Launch.
For both events the pageName in digitalData.page.pageInfo.pageName should include the accurate name of the page.
# Analytics Variables & Events
On page_view event, the sponsorship eVars and props are set based on the pageName. If the pageName contains Children List Sponsorship then the search variables are set. If the pageName contains Child Profile Sponsorship then the child product view variables and event are set.
# Child Search
On child search and child list page view display the following variables are set: eVar33,eVar35,eVar37,eVar67,prop48,prop60.
On child_search_result_click event, event56 is set. On page_view event, no custom events are set, standard page view event are set only.
# Child Profile
On child profile page view display the following variables are set: eVar34,eVar35,eVar38,eVar56,eVar67,prop48,prop60.
No custom events are set, standard page view event are set only.
# Page Name Pattern
# Child List/Search
${locationOrGroup} Children List Sponsorship
${locationOrGroup} - optional location or SOG group denoting the landing page, current values are US and Refugee
# Child Profile Page
${group} Child Profile Sponsorship
${group} - optional SOG group that has a special landing page, current value is Refugee
# Page View Only Event Conditions
# First Page Visit
The user has no history of visiting other sponsorship pages, the app router's previous path is not defined. The URL of the page doesn't contain any valid search parameters.
- If the user loaded the default child sponsorship list page.
Test cases: - If the user came to the page for the first time and URL parameters include only
display_type=refugeeandsogordisplay_type=usandlocationbut no others.
Test cases: - The user loaded a child page.
Test cases: - If the user came to the page for the first time with valid URL search parameter(s).
Test cases:
# Subsequent Page Visits
The user has a history of visiting other sponsorship pages, the app router's previous path is defined and has a valid value.
- If the user navigates between the list of children, searched or not and child profile page.
Test cases:- world children list (opens new window) -> child profile
- world children list (opens new window) -> search -> child profile
- US children list (opens new window) -> child profile
- US children list (opens new window) -> search -> child profile
- refugee children list (opens new window) -> child profile
- refugee children list (opens new window) -> search -> child profile
- If the user navigated from a child page to the list of children page by clicking on Find Another Child Button.
Test cases:- world child (opens new window) -> world children list
- US child (opens new window) -> world children list
- refugee child (opens new window) -> world children list
- If the user navigated from a child page to the list of children page by clicking on Find Another Refugee Child Button.
Test cases:- refugee child (opens new window)-> refugee children list
- If the user clicked on any sponsorship links in the main menu while on any sponsorship pages.
Test cases:- world children list (opens new window) -> US children menu click
- world children list (opens new window) -> refugee children menu click
- US children list (opens new window) -> world children menu click
- US children list (opens new window) -> refugee children menu click
- refugee children list (opens new window) -> world children menu click
- refugee children list (opens new window) -> US children menu click
# Search Only Event Conditions
The user has a history of visiting sponsorship child list pages, the app router's previous path is defined and is either search or children.
- If the user executed a search on a page, the search event will trigger.
Test cases:- world children list (opens new window) -> search
- US children list (opens new window) -> search
- refugee children list (opens new window) -> search