Umbraco.Community.Engage.LocationHeaders
0.1.1
dotnet add package Umbraco.Community.Engage.LocationHeaders --version 0.1.1
NuGet\Install-Package Umbraco.Community.Engage.LocationHeaders -Version 0.1.1
<PackageReference Include="Umbraco.Community.Engage.LocationHeaders" Version="0.1.1" />
<PackageVersion Include="Umbraco.Community.Engage.LocationHeaders" Version="0.1.1" />
<PackageReference Include="Umbraco.Community.Engage.LocationHeaders" />
paket add Umbraco.Community.Engage.LocationHeaders --version 0.1.1
#r "nuget: Umbraco.Community.Engage.LocationHeaders, 0.1.1"
#addin nuget:?package=Umbraco.Community.Engage.LocationHeaders&version=0.1.1
#tool nuget:?package=Umbraco.Community.Engage.LocationHeaders&version=0.1.1
Engage LocationHeaders
Engage - LocationHeaders is a lightweight package for Umbraco Engage that enriches analytics and segmentation data with location information extracted from HTTP headers.
The package is designed to work out-of-the-box on Umbraco Cloud, using location headers automatically injected by services like Cloudflare or Azure Front Door. This allows Engage to tap into geographic information such as country, region, and city, without the need for client-side geolocation or third-party services.
β¨ Features
- π Plug-and-play for Umbraco Cloud β no setup required
- π Supports Cloudflare, Azure Front Door, and other CDNs that inject location headers
- βοΈ Optional configuration for custom header names or alternative setups
- π Enables location-based segmentation and analytics in Umbraco Engage
Installation
Add the package to an existing Umbraco website (v13+) from nuget:
dotnet add package Umbraco.Community.Engage.LocationHeaders
π οΈ Configuration (Optional)
By default, the package expects certain common header names. If your setup uses different headers, you can override the defaults using appsettings configuration:
"Engage": {
"LocationHeaders": {
"Country": "uc-ipcountry",
"County": "CF-Region",
"Province": "CF-Region",
"City": "cf-ipcity"
}
}
If your infrastructure uses custom headers, you can override the defaults in your appsettings.json
file. Simply add an Engage:LocationHeaders
section with keys like Country
, County
, Province
, or City
and map them to your custom header names.
π Getting Started
Install the package via NuGet and deploy it to your Umbraco project. If youβre using a compatible CDN (like Cloudflare), the package will begin collecting location data immediately.
π§ Use Cases
- Segment content based on visitor location
- Build region-specific personalizations
- Enhance analytics with geographic insights
π¦ Package Compatibility
- Compatible with Umbraco 13.x
- Optimized for Umbraco Cloud
- Requires Umbraco Engage
Bring location awareness to your digital experiences with Engage - LocationHeaders β simple, configurable, and Umbraco Cloud-ready.
Contributing
Contributions to this package are most welcome! Please read the Contributing Guidelines.
π Acknowledgements
Big thanks to the community members who inspired and supported this package:
- π‘ @TvGessel β for the original idea of using location headers to enrich Umbraco Engage with geolocation data.
- π§° @LottePitcher β for providing the excellent Umbraco Package Starter Kit, which this package is built upon.
This package wouldnβt exist without your contributions β thank you!
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net8.0
- Umbraco.Cms.Core (>= 13.8.0)
- Umbraco.Engage.Core (>= 13.4.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.