Branding

Branding allows SEEK hirers to promote their company brand on their job ads. Not all SEEK ad products include branding; you can query the ad product’s features  to determine if branding is available.
A brand has four components:
  1. An opaque object identifier used to specify the brand when posting a job ad.
  2. A mandatory logo displayed on the hirer’s job ads and on SEEK’s Apply Form. This is represented as an AdvertisementBrandingImage  with a type code of OriginalLogo.
  3. An optional cover image displayed at the top of the hirer’s job ads. This is represented as an AdvertisementBrandingImage  with a type code of CoverImage.
  4. A display name used for the hirer’s reference when selecting and managing brands.
Brands on the SEEK employer website are identified visually using their logo & cover image. The brand’s name is rarely descriptive enough to uniquely identify the brand. SEEK recommends that your software presents hirers with a paginated list of brands that incorporates their logo, cover image & name.
Loading brands
Open in Storybook
Example code on GitHub
The SEEK API only supports listing and querying brands. Hirers must use the Logos & Brands section of the SEEK employer website to manage their brands.
You will receive an empty array when listing brands for a hirer that has none configured. In this scenario, you should display a call to action in place of the brand selection control. A localised deep link to the SEEK employer website can be queried from the AdvertisementBrandingsConnection.brandManagementUrl  field.
Loading brands
Open in Storybook
Example code on GitHub
When a hirer chooses an ad product that supports branding, your software is required to list their configured brands for selection. It is highly recommended but ultimately optional for the hirer to select a brand to apply to their job ad.
Hirers can set a default brand on the SEEK employer website, which is applied to job ads that support branding but were posted without one selected. This is handled transparently to your posting process.
When hirers create, update, or delete a brand, they expect the change to be reflected the next time they post a job ad. To support this, you should query the hirer’s current brands as part of your software’s job posting flow. If this isn’t possible you should provide a way for the hirer to manually refresh their brands from the SEEK API.

Before you begin

  • SEEK recommends using a browser token to query brands directly from a hirer’s browser. For the browser token to work, you will need to include the query:advertisement-brandings scope in your request.
  • You can also query brands from your backend using a partner token.

Operations

The SEEK API provides two queries for retrieving brands:
  1. advertisementBrandings returns a paginated list of brands for a given hirer.
  2. advertisementBranding returns a brand for a given brand object identifier.

advertisementBrandings

The advertisementBrandings query  returns a paginated list of brands for a given hirer.
QueryVariablesResult
CopyGraphQL Explorer
query ($after: String, $first: Int, $hirerId: String!) {
  advertisementBrandings(after: $after, first: $first, hirerId: $hirerId) {
    edges {
      node {
        id {
          value
        }
        name
        images {
          typeCode
          url
        }
      }
    }
    brandManagementUrl {
      url
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}
For subsequent queries you pass the previous page’s endCursor as the after argument. Once hasNextPage is false there are no more brands to page through.

advertisementBranding

The advertisementBranding query  returns the brand for a given brand object identifier.
QueryVariablesResult
CopyGraphQL Explorer
query ($id: String!) {
  advertisementBranding(id: $id) {
    id {
      value
    }
    name
    images {
      typeCode
      url
    }
  }
}
Ad selection: Testing
Job posting features: Application methods