Goals allow you to define important Website actions that AIUNIFY Analytics should treat as conversions.
The system describes Goals as a way to:
“Track specific events of your visitors, such as button clicks or form submissions or even page visits.”
A Goal helps transform ordinary Website activity into a measurable business outcome.
For example:
Visitor reaches Thank-You Page → Conversion
or:
Visitor clicks Request Demo → Conversion
or:
Visitor completes a custom Website action → Conversion
AIUNIFY Analytics provides two Goal triggers:
A Goal identifies an action you consider important enough to measure separately from general Website traffic.
The application's Help section explains that Goals can track actions such as:
The basic relationship is:
Website Activity → Goal Trigger Occurs → Goal Conversion Recorded
Normal Analytics tells you what happened on your Website.
For example:
Goals tell you which activities represented a desired outcome.
For example:
This makes Goals especially important when measuring business results, rather than traffic alone.
To open Goals:
The sidebar links directly to the Website's Goals reporting area.
The page displays:
Goals
along with its Goal-reporting controls and conversion information.
Goals are supported for both:
The Analytics reporting system retrieves Goals and their Conversion counts for either Website Tracking Type.
However, the amount of Visitor-level context available around a conversion differs.
A Goal Conversion can be associated with:
A Goal Conversion can still be recorded, but it does not have the same persistent Visitor relationship.
This distinction becomes important when analyzing who converted and the journey leading to the conversion.
The Goals page contains two primary reporting elements:
The chart visualizes Goal Conversions over the selected reporting period.
Below it, the Goals area lists individual Goals and their Conversion performance.
The Goal chart is labeled using:
Conversions
and plots the number of recorded Goal Conversions across the selected Date Range.
This allows you to see when conversions occurred.
For example:
The chart is useful for identifying:
The Goals page uses the standard Analytics Date Range control.
You can select reporting periods such as:
The Goal Conversion chart and Goal Conversion counts use the selected reporting dates.
Each Goal in the Goals area displays:
The system calculates each Goal's percentage from:
Goal Conversions ÷ Total Conversions across displayed Goals
Suppose you have three Goals:
Request Demo — 50 Conversions
Newsletter Signup — 30 Conversions
Download Brochure — 20 Conversions
Total:
100 Conversions
The Goals area could therefore represent:
Request Demo → 50%
Newsletter Signup → 30%
Download Brochure → 20%
This makes it easy to compare which Goals are producing the greatest share of tracked conversions.
AIUNIFY Analytics orders Goals according to their Conversion totals, with the Goals producing the most conversions appearing first.
This helps you quickly identify your highest-performing tracked outcomes.
To create a Goal:
The Goal creation window is titled:
Create a goal
and explains:
“Track conversions or specific actions such as button clicks or form submissions.”
The Create button is available when your Analytics account allows additional Goals.
If the Website has reached its Goal limit, the Create control becomes disabled and displays the applicable account feature-limit notice.
Availability: The number of Goals you can create may depend on the features or limits enabled for your AIUNIFY Analytics account.
The first selection in Create a goal determines the:
Goal trigger
Available options are:
Your selection determines what additional information you must provide.
Select:
Pageview
when reaching a particular Website page should count as a Conversion.
The AIUNIFY Analytics Help section explains:
“The pageview goal is easy to set up. It converts when a visitor reaches a specified page.”
This is the simplest Goal Type.
A common conversion process is:
Visitor completes form
↓
Website redirects to:
/thank-you
↓
AIUNIFY Analytics detects /thank-you
↓
Goal Conversion
The application's own Help example specifically identifies a thank-you page following:
as a Pageview Goal use case.
When you select Pageview, the Create Goal form asks for:
The Website host/path is displayed before the Page Path field.
For example:
Website:
example.com/
Page Path:
thank-you
creates the intended Goal location:
example.com/thank-you
Enter a descriptive Name.
Examples:
The Name is required. AIUNIFY Analytics will not create the Goal if the Name field is empty.
Choose a name that communicates the business outcome rather than only the technical page.
For example:
Better:
Quote Request Complete
rather than:
Less descriptive:
Thank You Page
For a Pageview Goal, enter the:
Page path
The form uses the placeholder:
thank-you
and automatically shows the Website address in front of the field.
For example:
Website:
example.com/
Goal Path:
thank-you
Target:
example.com/thank-you
AIUNIFY Analytics validates Pageview Goal Conversions against the configured Website path and the Goal's specific Page Path.
Therefore, configure the Page Path to match the actual conversion page used by the Website.
For example, if the real confirmation page is:
/form-complete
do not configure:
/thank-you
unless that is actually where the visitor is sent.
Pageview Goals work well when completing an action reliably sends the visitor to a unique page.
Examples include:
Lead Form
/quote-request
↓
/quote-complete
Registration
/register
↓
/registration-success
Purchase
/checkout
↓
/order-complete
The destination page becomes the measurable conversion point.
Choose a page that represents the intended action as specifically as possible.
For example, using:
/contact
as a Conversion Goal may count visitors merely viewing the Contact page.
Using:
/contact-complete
after successful submission more accurately represents:
Contact Form Completed
when your Website uses that workflow.
After entering:
click:
Create
AIUNIFY Analytics creates the Goal and returns you to the Goals reporting area.
Select:
Custom event
when the action you want to measure cannot be identified simply by reaching a specific Website page.
The system Help states:
Custom goals require extra code
and are intended for actions not covered by Pageview Goals.
AIUNIFY Analytics identifies Custom Goal examples including:
This makes Custom Event Goals more flexible than Pageview Goals.
When you select:
Custom event
the Goal form displays:
The Javascript Code field is automatically generated from the Goal Key.
The:
Key
acts as the Custom Goal's unique identifier.
The form provides a generated value and uses the placeholder:
custom-identifier
You can replace it with a meaningful identifier.
Examples might include:
request-demo
download-brochure
application-submit
pricing-button
contact-submit
Use a clear, stable Key because your Website code will trigger the Goal using that identifier.
When creating a Custom Goal, Analytics converts the Key into a URL-friendly identifier format before storing it.
If the field does not contain a usable Key, Analytics can generate one automatically.
For normal operation, choose a short and recognizable Key yourself.
The Custom Goal form automatically generates:
Javascript code
based on the Goal Key.
The field is read-only and the system explains:
“This JavaScript snippet allows you to activate custom events within your web app.”
As you change the Key, the generated JavaScript snippet is updated automatically.
After creating a Custom Event Goal, your Website must trigger the supplied JavaScript when the intended action occurs.
Use the exact JavaScript Code generated by your AIUNIFY Analytics Goal window.
Do not manually guess or recreate the Analytics function name.
The system's Help explains that when the generated Goal code executes:
the Goal Conversion is recorded.
Suppose you want to track:
Request Demo button clicks
Create:
Goal Trigger: Custom event
Name: Request Demo Click
Key: request-demo
AIUNIFY Analytics generates the appropriate JavaScript code.
Your Website developer then connects that generated code to the Request Demo action.
The workflow becomes:
Visitor clicks Request Demo
↓
Website runs generated Goal code
↓
AIUNIFY Analytics receives Goal trigger
↓
Conversion recorded
The built-in AIUNIFY Analytics Help demonstrates that Goal code can be integrated directly into a Website button so the Goal triggers when the user interacts with it.
The exact method depends on the Website's own code and application structure.
If you are not responsible for your Website's JavaScript, provide the generated Goal code to your Website developer.
A simple way to decide is:
| Goal TypeBest Used When | |
| Pageview | Success is represented by reaching a specific page |
| Custom event | Success occurs through a specific interaction or JavaScript-detectable action |
For example:
Reached /thank-you
→ Pageview
Clicked Request Demo without leaving page
→ Custom event
Advanced form submitted without redirect
→ Custom event
Reached /order-complete
→ Pageview
Ask:
Does completing the action always send the visitor to a unique page?
Yes → Pageview Goal
No → Continue
Can the desired action be triggered or detected through Website JavaScript?
Yes → Custom Event Goal
This keeps Goal configuration as simple as possible.
AIUNIFY Analytics checks the number of Goals already created for the selected Website before creating another one.
If the Website has reached its available Goal limit, creation is prevented.
If Create is disabled, review your account's Goal availability rather than assuming the system is malfunctioning.
When the Goal trigger occurs and passes the applicable validation, AIUNIFY Analytics creates a:
Goal Conversion
record.
That Conversion is associated with:
For Advanced Tracking, it can additionally be linked to:
With Advanced Tracking, Goal Conversion data becomes part of the Visitor Journey.
The Conversion can be associated with the specific:
Visitor → Session → Event
that generated it.
This is why Chapter 13 could display Goal Conversions inside an individual Visitor record.
For an Advanced Tracking Website, AIUNIFY Analytics checks whether that Visitor has already converted the same Goal.
If a Conversion already exists for:
Visitor + Website + Goal
the application does not create another Conversion for that same Visitor and Goal.
This is an important reporting behavior.
For example:
A Visitor reaches:
/thank-you
today and then reaches the same Goal again later.
For that Advanced Visitor, the same Goal is not repeatedly counted as a new Conversion.
Suppose:
Visitor A converts Request Demo.
They later refresh or revisit the conversion page.
Without duplicate protection, one person could create several apparent conversions.
For Advanced Tracking, AIUNIFY Analytics protects the Goal count by checking whether that Visitor has already converted that Goal.
This makes the Goal more representative of:
Visitors who achieved the Goal
rather than simple repeated triggering by the same identified Visitor.
Lightweight Tracking does not use the same persistent Visitor identity.
When a valid Lightweight Goal Conversion event is received, Analytics records the Goal, Website, expiration information, and Conversion Date.
Because Lightweight Tracking does not have the Advanced Visitor relationship, do not expect:
to behave the same way.
The Goals area counts recorded Conversions for each Goal within the selected Date Range.
The system queries each Goal and counts its associated Conversion records for the current Website and reporting period.
For example:
Request Demo — 15
means AIUNIFY Analytics recorded 15 Goal Conversions matching that Goal and reporting period.
The line chart plots total recorded Goal Conversions by time across the selected reporting period.
Use it to answer questions such as:
Inside the Goals list, the Goal Name is clickable.
Selecting the Goal Name opens:
Edit goal
This allows you to modify the Goal after creation.
To edit a Goal:
The Edit Goal window retains the Goal's existing Trigger Type and displays the fields appropriate for that Goal.
For a Pageview Goal, you can update:
For example:
Old Path:
thank-you
New Path:
request-complete
After changing the path, click:
Update
For a Custom Event Goal, you can update:
The Javascript code field updates according to the current Key.
Important: If you change a Custom Goal Key, review the Website implementation that triggers that Goal. Your Website code must use the correct current Goal identifier.
The Edit Goal window does not provide a Goal Trigger selector.
It preserves the Goal's existing Type and displays either:
or:
according to how the Goal was originally created.
Therefore, if you need to change a Goal from:
Pageview → Custom Event
or:
Custom Event → Pageview
create a new Goal with the correct Trigger Type rather than expecting to switch the existing Goal's Type.
If your Website changes its conversion page:
Old
/thank-you
New
/submission-complete
update the Pageview Goal accordingly.
Otherwise, visitors may reach the new page without satisfying the Goal's configured path validation.
AIUNIFY Analytics verifies a Pageview Goal against its configured Website path before recording the Conversion.
Changing a Custom Goal Key also changes the JavaScript code generated by the Edit Goal window.
After changing it:
Failure to update the Website-side trigger can cause the new Goal Key and the Website implementation to stop matching.
The Edit goal window also contains:
Delete
for owner-level access.
To delete:
The system then refreshes its Goal information.
Only delete a Goal when you no longer need that Goal configuration.
Goal creation and destructive Goal-management actions are restricted when Analytics is being operated through Team context.
The Goal-management controller blocks Create, Update, and Delete operations in Team context.
This allows shared Analytics visibility while protecting owner-level Goal configuration.
For Advanced Tracking, Goal Conversions can be reviewed inside individual Visitor records.
As covered in Chapter 13:
Visitor
→ Sessions
→ Session Events
→ Goals conversions
This allows you to investigate what happened before a Visitor achieved a Goal.
Suppose your business Website contains a Quote Request form.
After successful submission, visitors are sent to:
/quote-complete
Create:
Goal Trigger: Pageview
Name: Quote Request Complete
Page Path: quote-complete
Your measurement becomes:
Visitor submits Quote Request
↓
Visitor reaches /quote-complete
↓
Conversion recorded
Now you can compare:
Traffic → Quote Request Conversions
rather than simply counting visits to the form itself.
Website flow:
/newsletter
↓
Visitor submits form
↓
/newsletter-thank-you
Create:
Goal Trigger: Pageview
Name: Newsletter Signup
Page Path: newsletter-thank-you
This measures successful completion rather than merely visits to the signup page.
Suppose your Website has:
Schedule Consultation
and clicking it opens an external scheduling application without first reaching a unique internal success page.
A Custom Event may be more appropriate.
Create:
Goal Trigger: Custom event
Name: Schedule Consultation Click
Key: schedule-consultation
Then connect the generated JavaScript code to the intended Website interaction.
Suppose a Website form submits dynamically and stays on the same page.
Because there is no unique confirmation-page Pageview, use:
Custom event
AIUNIFY Analytics explicitly identifies advanced form submissions as a Custom Goal use case.
Your Website implementation triggers the generated Goal code after the desired successful action.
Suppose you offer:
Download Product Guide
and the download does not lead to a unique success page.
Create a Custom Goal representing the intended download action.
This lets you distinguish:
Pageviews of Download Page
from:
Actual tracked Download action
provided your Website implementation triggers the Custom Goal at the appropriate time.
Do not automatically create a Custom Goal for every external link.
AIUNIFY Analytics already provides:
Outbound Clicks
for general external-link measurement.
Use a Goal when the particular interaction represents a meaningful Conversion.
For example:
Click Facebook icon
→ probably ordinary Outbound Click
Click Complete Application on external portal
→ may be important enough to also represent a Custom Goal, depending on your measurement strategy
Advanced Visitor Events can record:
Form Submission
as behavioral activity.
A Goal serves a different purpose.
Answers:
Did this supported interaction occur during the Session?
Answers:
Did the visitor complete the business outcome we defined as a Conversion?
Not every tracked form interaction necessarily needs to be a Goal.
Similarly:
Track visits to Website pages.
Identify specific Pageviews that represent a Conversion outcome.
For example:
/pricing
may simply be a Pageview.
/purchase-complete
may be both:
Pageview + Goal Conversion
The Goals screen shown in the supplied source provides:
The source does not establish a dedicated user-facing Conversion Rate percentage calculated as:
Conversions ÷ Visitors
on this Goals screen.
Therefore, do not confuse the percentage displayed beside each Goal with a traditional conversion rate.
The displayed percentage represents that Goal's share of the total conversions shown in the Goals list.
After creating a Pageview Goal:
For an Advanced Website, you can also inspect the Visitor's Goals conversions history.
After implementing a Custom Event Goal:
If no Conversion appears, verify that the Website is actually executing the current code for the correct Goal Key.
If a Goal remains at zero, check:
Make sure you are viewing the Website where the Goal was created.
Confirm:
Websites → Edit → Tracking
is active.
The Website must be connected to AIUNIFY Analytics.
Make sure the test Conversion occurred within the selected reporting period.
Confirm Pageview vs. Custom Event matches your implementation.
Check:
AIUNIFY Analytics checks the actual Website URL against the configured Pageview Goal path before accepting the Conversion.
Check:
The system generates Custom Goal code from the current Key.
This may be expected.
Advanced Tracking prevents the same persistent Visitor from generating multiple Conversion records for the same Goal.
If you repeatedly test the same Goal using the same Advanced Visitor identity, the Conversion count may not continue increasing.
This behavior protects against duplicate Conversions from the same Visitor and Goal.
If Create is disabled:
The Goals interface disables creation when the applicable Website Goal limit has been reached.
Use business-outcome names.
Good examples:
Avoid vague Goal names such as:
Clear naming makes Goal reports much easier to understand later.
Do not create Goals for every possible Website interaction.
Focus first on actions that matter to the business.
A useful hierarchy is:
Primary Conversions
Secondary Conversions
Behavioral Activity
This keeps your Goal reporting focused on measurable outcomes rather than becoming a duplicate of general Analytics.
For a sales-oriented Website, useful Goals may include:
The exact Goal Type depends on the Website flow.
Potential Goals could include:
Where completion results in a unique URL, a Pageview Goal may be simplest.
Where it occurs dynamically without a unique URL, consider a Custom Event Goal.
Potential Goals include:
The Goal should represent the action that has business value—not simply the page containing the call to action.
For ongoing Goal analysis:
For Advanced Tracking:
Goal Conversion
↓
Visitor
↓
Session
↓
Pageviews
↓
Session Events
↓
Replay when available
This lets you analyze not only:
How many conversions occurred?
but:
What behavior led to those conversions?
When creating or reviewing a Goal, confirm:
The AIUNIFY Analytics Goal process can be summarized as:
Define Business Outcome
↓
Create Goal
↓
Choose:
Pageview
or
Custom Event
↓
Configure Page Path or Custom Key
↓
Install/Implement Trigger if Required
↓
Visitor Performs Action
↓
Goal Conversion Recorded
↓
Conversions Chart and Goal Totals Updated
↓
For Advanced Tracking:
Conversion → Visitor → Session → Journey
You should now understand how AIUNIFY Analytics uses Goals to turn Website behavior into measurable Conversion outcomes.
The system provides two Goal Triggers:
Pageview for conversions represented by reaching a specified Website page, and Custom event for actions that require a JavaScript-triggered conversion.
The Goals screen then displays recorded Conversions over time and ranks individual Goals according to their Conversion counts.
With Advanced Tracking, Goal Conversions can also be linked back to the individual Visitor, Session, and Event responsible for the Conversion, allowing complete conversion-journey analysis.