zernio-sdk 0.0.550 → 0.0.552

data/spec/api/ad_insights_api_spec.rb

@@ -0,0 +1,120 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Zernio::AdInsightsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'AdInsightsApi' do
+  before do
+    # run before each test
+    @api_instance = Zernio::AdInsightsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of AdInsightsApi' do
+    it 'should create an instance of AdInsightsApi' do
+      expect(@api_instance).to be_instance_of(Zernio::AdInsightsApi)
+    end
+  end
+
+  # unit tests for create_ad_insights_report
+  # Submit an async insights report run
+  # Submits an asynchronous Meta insights report. Same query surface as GET /v1/ads/insights, but in the JSON body; Meta processes the report server-side, which is the right choice for long ranges or large accounts where the sync query is slow or rate-limited. Returns a `reportRunId` to poll via GET /v1/ads/insights/reports/{reportRunId}. 
+  # @param create_ad_insights_report_request 
+  # @param [Hash] opts the optional parameters
+  # @return [CreateAdInsightsReport202Response]
+  describe 'create_ad_insights_report test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_ad_analytics
+  # Get ad analytics
+  # Returns detailed performance analytics for an ad. Includes summary metrics, a daily timeline over the requested date range, and optional demographic breakdowns (Meta and TikTok only). If no date range is provided, defaults to the last 90 days. Date range is capped at 730 days max. 
+  # @param ad_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Date] :from_date Start of date range (YYYY-MM-DD). Defaults to 90 days ago.
+  # @option opts [Date] :to_date End of date range (YYYY-MM-DD). Defaults to today. Max 730-day range.
+  # @option opts [String] :breakdowns Comma-separated breakdown dimensions.  **Meta**: age, gender, country, publisher_platform, device_platform, region.  **TikTok**: gender, age, country_code, platform, ac, language.  **LinkedIn** (firmographics): job_title, job_function, seniority, industry, company, company_size, country, region. Rows carry the raw pivot `value` plus a resolved `name`. LinkedIn serves these aggregated over the whole range, delays the data 12-24h, and omits segments with fewer than 3 events. 
+  # @return [GetAdAnalytics200Response]
+  describe 'get_ad_analytics test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_ad_insights_report
+  # Poll an async insights report run
+  # Status and results for a report run created via POST /v1/ads/insights/reports. While the job runs, returns `status` and `percentCompletion`. Once `status` is \"Job Completed\" the response also carries a `data` page, cursor-paginated via `limit` / `after`. 
+  # @param report_run_id 
+  # @param account_id Zernio SocialAccount id used to resolve the Meta token (must be the same connection that created the run).
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :limit 
+  # @option opts [String] :after 
+  # @return [GetAdInsightsReport200Response]
+  describe 'get_ad_insights_report test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_campaign_analytics
+  # Get campaign analytics
+  # Returns performance analytics for a whole campaign in one call: summary metrics, a daily timeline over the requested date range (summed across the campaign's ads), and optional demographic breakdowns. Breakdowns are fetched live from Meta at the campaign level (one call per dimension, no per-ad fan-out), so an agency dashboard gets campaign-level age/gender/etc. without summing thousands of per-ad reads. `campaignId` is the platform campaign id; pass `platform` when a campaign id could be ambiguous across platforms. If no date range is provided, defaults to the last 90 days. Date range is capped at 730 days max. 
+  # @param campaign_id Platform campaign id (platformCampaignId).
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :platform Disambiguate when the campaign id exists across platforms (e.g. facebook, instagram).
+  # @option opts [Date] :from_date Start of date range (YYYY-MM-DD). Defaults to 90 days ago.
+  # @option opts [Date] :to_date End of date range (YYYY-MM-DD). Defaults to today. Max 730-day range.
+  # @option opts [String] :breakdowns Comma-separated breakdown dimensions.  **Meta**: age, gender, country, publisher_platform, device_platform, region, platform_position, impression_device, video_asset, image_asset, body_asset, title_asset.  **LinkedIn** (firmographics): job_title, job_function, seniority, industry, company, company_size, country, region. Rows carry the raw pivot `value` plus a resolved `name`. LinkedIn serves these aggregated over the whole range, delays the data 12-24h, and omits segments with fewer than 3 events. 
+  # @return [GetCampaignAnalytics200Response]
+  describe 'get_campaign_analytics test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for query_ad_insights
+  # Flexible live insights query
+  # Live, flexible insights query against Meta's Graph API. Unlike GET /v1/ads/{adId}/analytics (fixed metric set, cached), this forwards caller-chosen `fields`, `breakdowns` and `filtering` to any Meta insights node and returns Meta's rows verbatim.  `objectId` selects the node: an ad account, campaign, ad set or ad platform id. `level` sets row granularity independently of the node.  Semantic validation is Meta's: an unknown field or invalid breakdown combination returns a 400 carrying Meta's message. For long ranges or agency-scale accounts prefer the async variant (POST /v1/ads/insights/reports). 
+  # @param account_id Zernio SocialAccount id (posting or ads variant) used to resolve the Meta token.
+  # @param object_id Meta insights node: act_<n>, campaign id, ad set id or ad id.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :level Row granularity
+  # @option opts [String] :fields Comma-separated Graph insights fields (e.g. spend,impressions,frequency,website_purchase_roas). Omitted = Meta's default set.
+  # @option opts [String] :breakdowns Comma-separated Graph breakdowns (e.g. age,gender or publisher_platform).
+  # @option opts [String] :action_breakdowns Comma-separated Graph action breakdowns. Segments the actions[] arrays in each row.
+  # @option opts [String] :action_attribution_windows Comma-separated Meta attribution windows. Action values are returned keyed per window.
+  # @option opts [String] :action_report_time When actions are counted: impression, conversion or mixed.
+  # @option opts [Boolean] :use_unified_attribution_setting Use the ad sets' own attribution settings for action counting.
+  # @option opts [String] :filtering JSON array of Meta filter objects: [{\"field\", \"operator\", \"value\"}]. Applied server-side by Meta.
+  # @option opts [String] :date_preset Meta date_preset (e.g. last_7d, last_30d, this_month). Mutually exclusive with fromDate/toDate.
+  # @option opts [Date] :from_date Start of range (YYYY-MM-DD); requires toDate.
+  # @option opts [Date] :to_date End of range (YYYY-MM-DD); requires fromDate.
+  # @option opts [String] :time_increment Days per row (1-90), monthly, or all_days.
+  # @option opts [Integer] :limit Rows per page
+  # @option opts [String] :after Cursor from paging.after of the previous page.
+  # @return [QueryAdInsights200Response]
+  describe 'query_ad_insights test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/ad_targeting_api_spec.rb

@@ -0,0 +1,101 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Zernio::AdTargetingApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'AdTargetingApi' do
+  before do
+    # run before each test
+    @api_instance = Zernio::AdTargetingApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of AdTargetingApi' do
+    it 'should create an instance of AdTargetingApi' do
+      expect(@api_instance).to be_instance_of(Zernio::AdTargetingApi)
+    end
+  end
+
+  # unit tests for estimate_ad_reach
+  # Estimate audience reach
+  # Returns a normalized pre-flight audience-size estimate for a targeting spec, before any campaign is created. Backed by each platform's native reach API (Meta `delivery_estimate`, LinkedIn `audienceCounts`, X `audience_summary`, Pinterest `audience_sizing`).  Platforms without a usable pre-flight reach API (Google Search/Display, TikTok) return `available: false` with no bounds, so clients can hide or grey out the estimate rather than treat the absence as an error. 
+  # @param estimate_ad_reach_request 
+  # @param [Hash] opts the optional parameters
+  # @return [EstimateAdReach200Response]
+  describe 'estimate_ad_reach test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_linked_in_bid_pricing
+  # Suggested bid and budget bounds
+  # LinkedIn-only. Returns the suggested bid and bid limits for a targeting spec, plus the daily-budget bounds LinkedIn will accept. Use it before creating a campaign to pick a bid inside the allowed range and warn the user if their daily budget is below the minimum. Wraps LinkedIn's `adBudgetPricing` finder.  Non-LinkedIn accounts return `available: false` so clients can hide the pricing UI without treating it as a failure. 
+  # @param get_linked_in_bid_pricing_request 
+  # @param [Hash] opts the optional parameters
+  # @return [GetLinkedInBidPricing200Response]
+  describe 'get_linked_in_bid_pricing test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_linked_in_supply_forecast
+  # Impressions, clicks and spend forecast
+  # LinkedIn-only. Forecasted impressions, clicks, spend and ~20 other metrics for a targeting spec over a time range. Wraps LinkedIn's `adSupplyForecasts` finder.  Each returned series carries a `metricType` (IMPRESSION, CLICK, SPENDING, MAX_POTENTIAL_BUDGET, COST_PER_MILLION_IMPRESSIONS, ...) and a `granularity` (DAILY, SEVEN_DAY, THIRTY_DAY, CUSTOM). LinkedIn caps the daily spending forecast at 1.2x the daily budget and returns 0 once the total budget is exhausted.  Non-LinkedIn accounts return `available: false`. 
+  # @param get_linked_in_supply_forecast_request 
+  # @param [Hash] opts the optional parameters
+  # @return [GetLinkedInSupplyForecast200Response]
+  describe 'get_linked_in_supply_forecast test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for search_ad_interests
+  # Search targeting interests
+  # Deprecated alias for `GET /v1/ads/targeting/search?dimension=interest`. Kept for backward compatibility, it returns the legacy `{ interests: [...] }` shape rather than the normalized `{ results: [...] }`. New integrations should use `GET /v1/ads/targeting/search` with `dimension=interest`. 
+  # @param q Search query
+  # @param account_id Social account ID
+  # @param [Hash] opts the optional parameters
+  # @return [SearchAdInterests200Response]
+  describe 'search_ad_interests test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for search_ad_targeting
+  # Search targeting options
+  # Resolve a human-readable query into the platform's opaque targeting ids used in the `TargetingSpec` (`countries`/`regions`/`cities`/`zips`/`metros` geo keys, and `interests`/`behaviors` entity ids) on `POST /v1/ads/create`, `POST /v1/ads/targeting/reach-estimate`, and `saved_targeting` audiences.  The `dimension` param selects what is searched, `geo` (locations, further scoped by `geoType`), `interest`, `behavior`, or `income`. Availability of each dimension varies by platform (e.g. behaviours are Meta/TikTok only). Results are normalized across platforms into a single shape, so the same client code consumes Meta, TikTok, LinkedIn, X, Pinterest, and Google results.  TikTok geo searches return every matching level in one list (`type` is `country`, `region`, `city`, `district`, or `metro` for DMA areas) — `geoType` is not applied. Results are scoped to the advertiser's targetable markets, and every id is usable in `regions`/`cities`/`metros` keys on `POST /v1/ads/create`.  For geo queries, `q` should contain only the locality name (e.g. `\"Amsterdam\"`, not `\"Amsterdam, NL\"`). Use `countryCode` to disambiguate. 
+  # @param account_id Social account ID (a connected account on the target ad platform).
+  # @param q Search query. For geo, the locality name only (no region/country suffix).
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :dimension What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
+  # @option opts [String] :geo_type Only used when `dimension=geo`. The kind of location to resolve. Defaults to `city`.
+  # @option opts [String] :country_code ISO 3166-1 alpha-2 country code (e.g. NL) to scope a geo search.
+  # @option opts [Integer] :limit Maximum results to return.
+  # @return [SearchAdTargeting200Response]
+  describe 'search_ad_targeting test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/analytics_api_spec.rb

@@ -347,12 +347,12 @@ describe 'AnalyticsApi' do
 
   # unit tests for get_you_tube_daily_views
   # Get YouTube daily views
-  # Returns daily view counts for a YouTube video including views, watch time, and subscriber changes. Requires yt-analytics.readonly scope (re-authorization may be needed). Data has a 2-3 day delay. Max 90 days, defaults to last 30 days. 
+  # Returns daily view counts for a YouTube video including views, watch time, and subscriber changes. Requires yt-analytics.readonly scope (re-authorization may be needed). YouTube finalizes analytics with a ~3-day delay; by default only finalized days are returned, and an explicit endDate can reach into the delay window (see the endDate parameter). Max 90 days, defaults to last 30 days. 
   # @param video_id The YouTube video ID (e.g., \"dQw4w9WgXcQ\")
   # @param account_id The Zernio account ID for the YouTube account
   # @param [Hash] opts the optional parameters
   # @option opts [Date] :start_date Start date (YYYY-MM-DD). Defaults to 30 days ago.
-  # @option opts [Date] :end_date End date (YYYY-MM-DD). Defaults to 3 days ago (YouTube data latency).
+  # @option opts [Date] :end_date End date (YYYY-MM-DD). Defaults to 3 days ago, the newest fully finalized day (YouTube finalizes analytics with a ~3-day delay). An explicit endDate is honored up to today: days inside the delay window are provisional and may still be revised by YouTube (see provisionalSince in the response), and days YouTube has not processed yet are omitted from dailyViews. 
   # @return [YouTubeDailyViewsResponse]
   describe 'get_you_tube_daily_views test' do
     it 'should work' do
@@ -368,7 +368,7 @@ describe 'AnalyticsApi' do
   # @option opts [String] :video_id YouTube video ID. When provided, demographics are scoped to this single video (must belong to the connected channel; otherwise 404 video_not_found). 
   # @option opts [String] :breakdown Comma-separated list of demographic dimensions: age, gender, country. Defaults to all three if omitted. 
   # @option opts [Date] :start_date Start date in YYYY-MM-DD format. Defaults to 90 days ago, or to the video's publish date (lifetime) when videoId is provided. 
-  # @option opts [Date] :end_date End date in YYYY-MM-DD format. Defaults to 3 days ago (YouTube data latency). 
+  # @option opts [Date] :end_date End date (YYYY-MM-DD). Defaults to 3 days ago, the newest fully finalized day (YouTube finalizes analytics with a ~3-day delay). An explicit endDate is honored up to today: days inside the delay window are provisional and may still be revised by YouTube (see provisionalSince in the response). 
   # @return [YouTubeDemographicsResponse]
   describe 'get_you_tube_demographics test' do
     it 'should work' do
@@ -383,7 +383,7 @@ describe 'AnalyticsApi' do
   # @param account_id The Zernio account ID for the YouTube account
   # @param [Hash] opts the optional parameters
   # @option opts [Date] :start_date Start date (YYYY-MM-DD). Defaults to the video's publish date (lifetime curve).
-  # @option opts [Date] :end_date End date (YYYY-MM-DD). Defaults to 3 days ago (YouTube data latency).
+  # @option opts [Date] :end_date End date (YYYY-MM-DD). Defaults to 3 days ago, the newest fully finalized day (YouTube finalizes analytics with a ~3-day delay). An explicit endDate is honored up to today: days inside the delay window are provisional and may still be revised by YouTube (see provisionalSince in the response). 
   # @return [YouTubeVideoRetentionResponse]
   describe 'get_you_tube_video_retention test' do
     it 'should work' do

data/spec/api/conversions_api_spec.rb

@@ -0,0 +1,199 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Zernio::ConversionsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ConversionsApi' do
+  before do
+    # run before each test
+    @api_instance = Zernio::ConversionsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ConversionsApi' do
+    it 'should create an instance of ConversionsApi' do
+      expect(@api_instance).to be_instance_of(Zernio::ConversionsApi)
+    end
+  end
+
+  # unit tests for add_conversion_associations
+  # Associate campaigns
+  # Associate one or more campaigns with this conversion rule. Returns a per-campaign success/failure result so callers can retry only the rows that failed (e.g. wrong campaign type for the rule's objective). 
+  # @param account_id 
+  # @param destination_id 
+  # @param add_conversion_associations_request 
+  # @param [Hash] opts the optional parameters
+  # @return [AddConversionAssociations200Response]
+  describe 'add_conversion_associations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for adjust_conversions
+  # Adjust uploaded conversions
+  # Adjust conversions that were previously uploaded via `POST /v1/ads/conversions` — retract them, restate their value, or enhance them with first-party data. Requires the Ads add-on.  **Google Ads only.** Google handles adjustments through the classic Google Ads API (`ConversionAdjustmentUploadService`); the Data Manager `ingestEvents` path used for sending conversions is ingest-only. Meta and LinkedIn have no equivalent, so this endpoint returns `405` for those platforms.  Adjustment types:  - `RETRACTION` — remove the conversion entirely (refund, chargeback, cancelled order, churn). - `RESTATEMENT` — change the conversion's value (upgrade / downgrade / partial refund). Send the corrected **total** value in `restatementValue` (not a delta). - `ENHANCEMENT` — attach first-party identifiers (hashed email / phone) to an existing conversion (enhanced conversions applied after the fact).  Identifying the original conversion (per adjustment):  - `orderId` — the transaction ID you sent as `eventId` on the original conversion. Recommended, and **required** for `ENHANCEMENT`. - or `gclid` + `conversionTime` — the click ID and the original conversion's time (unix seconds). Not available for `ENHANCEMENT`.  `destinationId` is the conversion action resource name, e.g. `customers/1234567890/conversionActions/987654321` (same value you send to `POST /v1/ads/conversions`). PII in `user` is hashed with SHA-256 server-side (Gmail-specific normalization included). Send plaintext.  Times are unix seconds; we convert to Google's required `yyyy-MM-dd HH:mm:ss+00:00` format. Up to 2000 adjustments per request; partial failure is supported (inspect `adjustmentsFailed` / `failures[]`). 
+  # @param adjust_conversions_request 
+  # @param [Hash] opts the optional parameters
+  # @return [AdjustConversions200Response]
+  describe 'adjust_conversions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_conversion_destination
+  # Create a conversion destination
+  # Create a new conversion destination on the platform. Supported for LinkedIn (conversion rule) and Google Ads (conversion action). Meta manages destinations in its own UI and returns 405.  **LinkedIn:** creation is NOT idempotent. A retry creates a second destination. Deduplicate before retrying.  **Google Ads:** calling with a name that already exists reuses the existing conversion action transparently (the response is identical to a fresh create). Calling with the same name but a different category returns a typed `IDEMPOTENCY_CONFLICT` (409) rather than silently returning the mismatched action.  **LinkedIn:** the rule is created with `conversionMethod=CONVERSIONS_API` and (by default) auto-associated with all of the ad account's campaigns via `autoAssociationType=ALL_CAMPAIGNS`. Pass `autoAssociationType: NONE` to opt out and manage associations explicitly via the associations endpoints below.  365-day attribution windows are only valid for `SUBMIT_APPLICATION`, `PURCHASE`, `ADD_TO_CART`, `QUALIFIED_LEAD`, and `LEAD` rule types; the API rejects other combinations locally.  **Google Ads:** the conversion action is created with `type=UPLOAD_CLICKS` (required for API-uploaded offline conversions, immutable after creation). The `type` field carries the Google `ConversionActionCategory` enum value, e.g. `PURCHASE`, `SUBSCRIBE_PAID`, `SIGNUP`, `IMPORTED_LEAD`, `BOOK_APPOINTMENT`. Unified standard event names (e.g. `Purchase`, `Subscribe`, `CompleteRegistration`, `Lead`, `Schedule`) are resolved to their Google category equivalents automatically. The action defaults to secondary (non-primary) to avoid immediately steering Smart Bidding; pass `primaryForGoal: true` to opt in. 
+  # @param account_id SocialAccount ID (linkedinads or googleads).
+  # @param create_conversion_destination_request 
+  # @param [Hash] opts the optional parameters
+  # @return [CreateConversionDestination201Response]
+  describe 'create_conversion_destination test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_conversion_destination
+  # Delete a conversion destination
+  # LinkedIn-only today. LinkedIn does not expose hard-delete on conversion rules — what their UI calls \"delete\" is the same `enabled: false` flip we apply here. The rule remains fetchable via GET with `status: 'inactive'`; the unified discovery endpoint hides it by default.  `adAccountId` may be passed as a query parameter (recommended) or as a JSON body field for clients that can send DELETE bodies. 
+  # @param account_id 
+  # @param destination_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :ad_account_id Required as query OR in JSON body.
+  # @return [nil]
+  describe 'delete_conversion_destination test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_conversion_destination
+  # Get a conversion destination
+  # LinkedIn-only today. Returns the full destination record for one conversion rule. The `adAccountId` query parameter is required because LinkedIn rules are scoped to a sponsored ad account. 
+  # @param account_id 
+  # @param destination_id 
+  # @param ad_account_id Numeric ID or full `urn:li:sponsoredAccount:{id}` URN.
+  # @param [Hash] opts the optional parameters
+  # @return [GetConversionDestination200Response]
+  describe 'get_conversion_destination test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_conversion_metrics
+  # Get attribution metrics
+  # LinkedIn-only today. Returns conversion-attribution metrics (`externalWebsiteConversions`, `externalWebsitePostClickConversions`, `externalWebsitePostViewConversions`, `conversionValueInLocalCurrency`, `qualifiedLeads`, `costInLocalCurrency`) bucketed by date.  Date-range constraints (passed through from LinkedIn): - `granularity=DAILY` is retained for ~6 months only - `granularity=ALL` with a range > 6 months auto-rounds to month boundaries - `granularity=MONTHLY`/`YEARLY` retains 24 months  Throttle: LinkedIn caps adAnalytics at 45M metric values per 5-minute window across the calling token. Single-rule queries are well within that limit; surfaces as 429 if hit. 
+  # @param account_id 
+  # @param destination_id 
+  # @param ad_account_id 
+  # @param start_date 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :end_date 
+  # @option opts [String] :granularity 
+  # @return [GetConversionMetrics200Response]
+  describe 'get_conversion_metrics test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_conversions_quality
+  # Get Event Match Quality
+  # Reads Meta Event Match Quality (EMQ) and pixel↔CAPI event coverage for a pixel/dataset, live from Meta's Dataset Quality API. Web events only (a Meta limitation). Meta-only; other platforms return 405. Requires the Ads add-on. 
+  # @param account_id SocialAccount _id (must be a metaads account).
+  # @param destination_id Meta pixel/dataset ID.
+  # @param [Hash] opts the optional parameters
+  # @return [GetConversionsQuality200Response]
+  describe 'get_conversions_quality test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_conversion_associations
+  # List associated campaigns
+  # LinkedIn-only today. Returns the campaigns currently associated with this conversion rule. Note that auto-association on rule creation runs once at create time; campaigns created after the rule still need explicit association. 
+  # @param account_id 
+  # @param destination_id 
+  # @param ad_account_id 
+  # @param [Hash] opts the optional parameters
+  # @return [ListConversionAssociations200Response]
+  describe 'list_conversion_associations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_conversion_destinations
+  # List conversion destinations
+  # Returns the list of pixels (Meta), conversion actions (Google), or conversion rules (LinkedIn) accessible to the connected ads account. Use the returned `id` as `destinationId` when posting to `POST /v1/ads/conversions`.  For Google and LinkedIn, each destination's `type` reflects the conversion type (PURCHASE, LEAD, SIGN_UP, etc.) — the event type is locked to the destination. For Meta, `type` is absent: pixels accept any event name per request.  For LinkedIn, destinations are returned across every sponsored ad account the connected token can access; the `adAccountId` field on each destination identifies the parent ad account and is required for subsequent CRUD calls (update, delete, associations, metrics). 
+  # @param account_id SocialAccount ID (metaads, googleads, linkedinads, or tiktokads).
+  # @param [Hash] opts the optional parameters
+  # @return [ListConversionDestinations200Response]
+  describe 'list_conversion_destinations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for remove_conversion_associations
+  # Remove associated campaigns
+  # Remove one or more campaign associations from this conversion rule. Pass `adAccountId` and `campaignIds` as query parameters (`campaignIds` is comma-separated). The route also accepts a JSON body with the same fields for clients that prefer DELETE-with-body, but the documented surface is query-only because some SDK code generators (e.g. Python) collapse query + body parameters with the same name into a single kwarg. 
+  # @param account_id 
+  # @param destination_id 
+  # @param ad_account_id 
+  # @param campaign_ids Comma-separated list of campaign IDs.
+  # @param [Hash] opts the optional parameters
+  # @return [RemoveConversionAssociations200Response]
+  describe 'remove_conversion_associations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for send_conversions
+  # Send conversion events
+  # Relay one or more conversion events to the target ad platform's native Conversions API. Platform is inferred from the provided `accountId`. Requires the Ads add-on.  Supported platforms:  - Meta (`metaads`) via Graph API - Google Ads (`googleads`) via Data Manager API `ingestEvents` - LinkedIn (`linkedinads`) via `/rest/conversionEvents` - TikTok (`tiktokads`) via the Offline Events API `/offline/batch/` — OFFLINE conversions only  `destinationId` semantics differ per platform:  - Meta: pixel (dataset) ID, e.g. `123456789012345` - Google: conversion action resource name, e.g. `customers/1234567890/conversionActions/987654321` - LinkedIn: conversion rule ID or URN, e.g. `104012` or `urn:lla:llaPartnerConversion:104012` - TikTok: Offline Event Set ID, e.g. `7057103914977558530`  TikTok notes: this path sends OFFLINE conversions (in-store / CRM / call-center), not web-pixel events. Each event must carry an email or phone (TikTok requires at least one). The connected TikTok ads account must have granted the Offline Events permission; older grants must reconnect.  Callers can list valid destinations via `GET /v1/accounts/{accountId}/conversion-destinations`.  All PII (email, phone, names, external IDs) is hashed with SHA-256 server-side per each platform's normalization spec, including Google's Gmail-specific dot/plus-suffix stripping. Send plaintext. LinkedIn `externalIds` are passed through as plaintext per LinkedIn's spec; only emails and phones are hashed.  For LinkedIn, the connected account must have been authorized after the Conversions API rollout (i.e. the OAuth grant must include `rw_conversions`). Older accounts must reconnect.  Batching is handled automatically. Meta caps at 1000 events per request and rejects the entire batch if any event is malformed. Google caps at 2000. LinkedIn caps at 5000 and is also all-or-nothing per chunk.  Dedup: pass a stable `eventId` on every event. Meta and LinkedIn use it to dedupe against browser-side pixel/Insight Tag events; Google maps it to `transactionId`.  Per-platform `eventName` semantics:  - Meta: free-form. Standard names (Purchase, Lead, ...) match Meta's built-in events; custom strings are accepted. - Google: ignored. The conversion action's category determines the event type. Send the standard name closest to your action for documentation, but the platform will not branch on it. - LinkedIn: ignored. The conversion rule's `type` (LEAD, PURCHASE, etc.) is locked to the destination at rule-creation time. Send the standard name for documentation; LinkedIn does not branch on it. 
+  # @param send_conversions_request 
+  # @param [Hash] opts the optional parameters
+  # @return [SendConversions200Response]
+  describe 'send_conversions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_conversion_destination
+  # Update a conversion destination
+  # Partial-update a conversion rule. LinkedIn-only today. Whitelisted fields: `name`, `enabled`, attribution windows, `valueType`, `value`, `attributionType`. The rule's `type` and parent ad account are intentionally not exposed for update — recreate the rule if those need to change. 
+  # @param account_id 
+  # @param destination_id 
+  # @param update_conversion_destination_request 
+  # @param [Hash] opts the optional parameters
+  # @return [GetConversionDestination200Response]
+  describe 'update_conversion_destination test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/lead_gen_api_spec.rb

@@ -0,0 +1,131 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Zernio::LeadGenApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'LeadGenApi' do
+  before do
+    # run before each test
+    @api_instance = Zernio::LeadGenApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of LeadGenApi' do
+    it 'should create an instance of LeadGenApi' do
+      expect(@api_instance).to be_instance_of(Zernio::LeadGenApi)
+    end
+  end
+
+  # unit tests for archive_lead_form
+  # Archive a lead form
+  # Meta has no hard delete for forms; this archives the form (status=ARCHIVED).
+  # @param form_id 
+  # @param account_id 
+  # @param [Hash] opts the optional parameters
+  # @return [ArchiveLeadForm200Response]
+  describe 'archive_lead_form test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_lead_form
+  # Create a lead form
+  # Creates a Lead Gen form on the connected Facebook Page (POST /{page-id}/leadgen_forms). NOT idempotent — a retry creates a second form. Prefilled question types (EMAIL, PHONE, FULL_NAME, …) must omit label/key; CUSTOM questions require both. Requires the Ads add-on. 
+  # @param create_lead_form_request 
+  # @param [Hash] opts the optional parameters
+  # @return [CreateLeadForm200Response]
+  describe 'create_lead_form test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_test_lead
+  # Create a test lead
+  # Submits a test lead against the form (POST /{form-id}/test_leads) to exercise retrieval without waiting for real ad impressions. Meta allows one test lead per form at a time. 
+  # @param form_id 
+  # @param create_test_lead_request 
+  # @param [Hash] opts the optional parameters
+  # @return [CreateTestLead200Response]
+  describe 'create_test_lead test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_lead_form
+  # Get a lead form
+  # @param form_id 
+  # @param account_id 
+  # @param [Hash] opts the optional parameters
+  # @return [GetLeadForm200Response]
+  describe 'get_lead_form test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_form_leads
+  # List leads for a single form
+  # Returns leads for one form. Serves persisted leads (ingested via the leadgen webhook) when available, falling back to a live Graph read. 
+  # @param form_id 
+  # @param account_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :limit 
+  # @option opts [String] :cursor 
+  # @option opts [Integer] :since Unix seconds.
+  # @return [ListFormLeads200Response]
+  describe 'list_form_leads test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_lead_forms
+  # List lead forms
+  # Lists the Lead Gen forms owned by the connected Facebook Page. Requires the Ads add-on.
+  # @param account_id Connected facebook account id.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :limit 
+  # @option opts [String] :cursor 
+  # @return [ListLeadForms200Response]
+  describe 'list_lead_forms test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_leads
+  # List submitted leads
+  # Returns persisted Meta Lead Gen leads for your team, newest-first, with keyset pagination on `cursor`. Leads are ingested in real time from the `leadgen` webhook. Requires the Ads add-on. 
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :form_id Filter to a single lead form.
+  # @option opts [String] :account_id Filter to a single connected account.
+  # @option opts [Integer] :limit 
+  # @option opts [Integer] :since Unix seconds; only leads created at/after this Meta timestamp.
+  # @option opts [String] :cursor Keyset cursor from a previous response's pagination.cursor.
+  # @return [ListLeads200Response]
+  describe 'list_leads test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end