datawebotGetheyfra Total Relief: product, bundle and offer records
Map Total Relief Magnesium Cream and its 1-, 3- and 6-jar offers; keep subscription, review, claim and return-policy records tied to their pages.
Getheyfra is the storefront; Total Relief is the named product
The Getheyfra storefront centers on Total Relief Magnesium Cream, a topical magnesium product. Brand, product and seller identity are not interchangeable fields here: the public pages use several names, so preserve each name with its exact page instead of silently merging seller records.
Scroll to compare →
| Identity field | Public-page example | How to keep it useful |
|---|---|---|
| Store/domain | Getheyfra at getheyfra.com | Retain the requested storefront name and canonical domain. |
| Named product | Total Relief Magnesium Cream | Keep this product family separate from jar-count offers and advertising pages. |
| About/footer attribution | The About page describes the HiRelief story; the footer reads “Total Relief - 2M Project LLC.” | Store the exact source page and displayed legal name with each seller attribution. |
| Terms/privacy/contact labels | Terms of Service names New World Project LLC; the Privacy Policy identifies Meritrelief and mentions HiRelief; SMS consent also says Meritrelief. | Do not normalize these names into a single legal entity without corroboration. |
Jar-count pages are separate from variants and recurring offers
Checked October 4, 2026: the public collection links to distinct 1-, 3- and 6-jar product pages. Their handles use month-supply wording, and the six-jar handle also mentions two free bonuses. The long-form page offers one-time and recurring purchase choices over repeated jar-count tiers. Keep each level separate.
Scroll to compare →
| Page or offer level | Getheyfra example | Keep these fields distinct |
|---|---|---|
| One-jar product page | /products/total-relief-magnesium-cream-1-month-supply | Product handle, stated jar count and any supply-duration wording. |
| Three-jar product page | /products/total-relief-magnesium-cream-3-month-supply | Three jars is a package quantity; do not turn it into a selectable cream formula or strength. |
| Six-jar page | /products/total-relief-magnesium-cream-6-month-supply-2-free-bonuses | Keep jar count, supply label and the “2 free bonuses” phrase as separate offer attributes. |
| Purchase mode | Long-form page shows one-time payment and Subscribe & Save options; its auto-refill copy describes a fresh supply every 30 days. | Store recurrence, discount wording and bundle quantity separately from the base product and any variant. |
Price, availability and ratings belong to a dated page snapshot
Getheyfra shows the same product through collection cards, bundle pages and long-form promotional flows. On the reviewed pages, status, offer values and rating widgets do not line up across those surfaces. A single “current price,” stock flag or review aggregate would erase the context a shopper needs.
Scroll to compare →
| Field | Observed page-level difference | Snapshot key |
|---|---|---|
| Displayed price | Collection and jar product pages show package prices, while the promotional offer page has separate one-time and Subscribe & Save tiers with different displayed amounts. | Capture URL, observation time, amount, currency context, package quantity, purchase mode and any compare-at value together. |
| Availability | Some product pages display “Sold out” while collection and promotional pages still show package cards or order buttons. | Bind status to the exact handle/offer and timestamp; do not carry it across all pages. |
| Rating and count | The homepage displays 4.9/5 from 1,000+ reviews; promotional pages show different 4.8 totals; bundle pages have their own review summaries (the reviewed three- and six-jar pages show 3.8/5 with different counts). | Keep rating, count, widget scope and source page together; do not merge review totals or copy testimonial text. |
Keep formula and benefit statements attached to their campaign pages
The catalog product name is stable, but the long-form pages contain sales claims, ingredient copy, endorsements and review blocks. During the October 4, 2026 review, two Getheyfra campaign variants described different magnesium percentages. Treat those as page-specific marketing statements until a matching package label resolves the difference.
Scroll to compare →
| Content type | Public-page example | Data boundary |
|---|---|---|
| Ingredient panel | A campaign page lists Magnesium Chloride, Glycerin, Aloe Vera Extract, lavender and rosemary oils, MSM, vitamin E, Arnica, vitamins B6 and D, and additional ingredients. | Keep the list with its source URL and version; compare with an exact package label before treating it as a universal formula. |
| Concentration claim | One campaign states 8% Nano-Magnesium Chloride; another says 20% magnesium chloride. | Record the claim verbatim with its campaign page; do not choose one as a verified product specification. |
| Marketing and endorsement | Campaign pages include health-benefit wording and at least one “Paid Endorser” label. | Separate attributed promotional copy, paid endorsements and customer reviews; do not present them as independently established effects. |
| Use disclaimer | The storefront footer says results vary, the product is for external use, and it is not intended to diagnose, treat, cure or prevent disease. | Keep the disclaimer attached to storefront claims. This source page does not provide medical advice or assess efficacy. |
The 90-day guarantee callout is not the full return-policy record
Product and campaign pages promote a 90-day guarantee in short, reassuring language. The published Refund Policy adds eligibility and documentation steps, including proof of purchase, a symptom log, application photos, return of jars and packaging, and a survey. Preserve the callout and policy as separate dated statements rather than treating the banner as a complete policy summary.
Scroll to compare →
| Policy record | Published-page detail | How to represent it |
|---|---|---|
| Offer callout | Product and campaign pages use “90-day money-back” or “full refund” wording. | Store as a page claim with its exact URL and capture date. |
| Refund policy | The policy describes proof/approval requirements and additional steps for the 90-day claim, including a symptom log, use photos, return of all jars/packaging and a survey. | Link to the policy and summarize only its posted terms; do not infer eligibility for an individual order or give a legal conclusion. |
| Customer/order data | The policy and privacy page discuss order identifiers, contact and shipping details, personal information and purchase history. | Exclude customer records, order details, payment data, submitted symptom logs, images and support conversations from public product data. |
Content reviewed 2026-10-04.